SPM + GTest
If you need to expose a C++ library with #gtest via #spm, there is a straightforward way to wrap existing tests with #xctest:
1. Add gmock as a .systemLibrary target in your Package.swift and link it to your .testTarget.
2. Create a module map and an umbrella header for gmock.
3. Create an Obj-C++ adapter that wraps GoogleTest with XCTestCase.
π CMD + U
![// Package.swift
let package = Package(
...
.systemLibrary(
name: "gmock",
path: "spm-support/gmock",
pkgConfig: "gmock", // -> /opt/homebrew/Cellar/googletest/.../lib/pkgconfig/gmock.pc
providers: [.brew(["googletest"])]), // Note: SPM does *not* invoke 'brew install'
...
.testTarget(
name: "targetTests",
dependencies: ["target", "gmock"],
path: "target/test"),
)
// spm-support/gmock/module.modulemap
module gtest [system] {
header "gmock.h"
link "gmock" // -> /opt/homebrew/Cellar/googletest/.../lib/libgmock.a
export *
}
// spm-support/gmock/gmock.h
#include <gmock/gmock.h>
// target/test/xctest_adapter.mm
#import <XCTest/XCTest.h>
#import <gmock/gmock.h>
@interface TargetTests : XCTestCase
@end
@implementation TargetTests
+ (void)initialize {
::testing::InitGoogleTest();
}
- (void)test_all {
XCTAssertEqual(0, RUN_ALL_TESTS());
}
// Or create a separate method for each GTest.
- (void)test_SomeGoogleTestFixture_SomeGoogleTest {
::testing::GTEST_FLAG(filter) = "SomeGoogleTestFixture.SomeGoogleTest";
XCTAssertEqual(0, RUN_ALL_TESTS());
}
@end](https://files.mastodon.social/media_attachments/files/114/714/590/193/443/841/original/e17724fd905677c1.png)
ΠΠΎΠΊΡΡΡΠΈΠ΅ ΠΏΡΠΎΡΠ΅Π΄ΡΡΠ½ΠΎΠ³ΠΎ ΠΊΠΎΠ΄Π° Π² ΠΠΠ ΠΏΡΠΎΠ΅ΠΊΡΠ΅ ΡΠ½ΠΈΡ-ΡΠ΅ΡΡΠ°ΠΌΠΈ Π² C++
Legacy ΠΏΡΠΎΠ΅ΠΊΡΡ Π½Π° Π‘++ Π·Π°ΡΠ°ΡΡΡΡ ΡΠ²Π»ΡΡΡΡΡ ΠΌΠ½ΠΎΠ³ΠΎΠΊΠΎΠΌΠΏΠΎΠ½Π΅Π½ΡΠ½ΡΠΌΠΈ, ΠΊΠΎΠ³Π΄Π° ΠΏΡΠΎΠ΄ΡΠΊΡ ΠΈΡΠΏΠΎΠ»ΡΠ·ΡΠ΅Ρ Π½Π΅ΡΠΊΠΎΠ»ΡΠΊΠΎ Π±ΠΈΠ±Π»ΠΈΠΎΡΠ΅ΠΊ, ΠΊΠΎΡΠΎΡΡΠ΅ ΠΈΠΌΠ΅ΡΡ ΡΠ°Π·Π»ΠΈΡΠ½ΡΡ Π°ΡΡ ΠΈΡΠ΅ΠΊΡΡΡΡ Π΄Π»Ρ ΡΠ°Π±ΠΎΡΡ Ρ Π½ΠΈΠΌΠΈ. ΠΠ±ΡΡΠ½ΠΎ ΡΡΠΎ: Π±ΠΈΠ±Π»ΠΈΠΎΡΠ΅ΠΊΠΈ, ΠΏΠΎΡΡΠ°Π²Π»ΡΠ΅ΠΌΡΠ΅ ΠΊΠ°ΠΊ ΠΠΠ ΡΠ΅ΡΠ΅Π½ΠΈΠ΅ (ΠΠ΅ΠΊΠΎΡΠΎΡΡΠ΅ ΠΌΠΎΠ΄ΡΠ»ΠΈ boost, SOCI ΠΊΠ°ΠΊ ΠΏΡΠΈΠΌΠ΅Ρ) Π±ΠΈΠ±Π»ΠΈΠΎΡΠ΅ΠΊΠΈ, ΡΠ΅Π°Π»ΠΈΠ·ΠΎΠ²Π°Π½Π½ΡΠ΅ Π² ΡΡΠ½ΠΊΡΠΈΠΎΠ½Π°Π»ΡΠ½ΠΎΠΌ ΡΡΠΈΠ»Π΅ (OpenGL ΡΠ΅ΡΠ΅Π· Π‘ API, POSIX ΠΊΠ°ΠΊ ΠΏΡΠΈΠΌΠ΅Ρ) ΠΠ·-Π·Π° ΡΡΠΎΠ³ΠΎ Π² ΠΈΡΠΎΠ³ΠΎΠ²ΠΎΠΌ ΠΏΡΠΎΠ΅ΠΊΡΠ΅ ΠΏΠΎΡΠ²Π»ΡΡΡΡΡ ΡΡΡΠ½ΠΎΡΡΠΈ, ΠΊΠΎΡΠΎΡΡΠ΅ Π²Π½ΡΡΡΠΈ ΡΠ΅Π°Π»ΠΈΠ·ΠΎΠ²Π°Π½Ρ ΡΠ΅ΡΠ΅Π· ΠΊΠ»Π°ΡΡΡ, Π½ΠΎ Π²Π½ΡΡΡΠΈ ΠΌΠ΅ΡΠΎΠ΄ΠΎΠ² ΠΊΠ»Π°ΡΡΠ° ΠΈΠ΄Π΅Ρ ΠΎΠ±ΡΠ°ΡΠ΅Π½ΠΈΠ΅ ΠΊ ΠΎΠ±ΡΡΠ½ΡΠΌ ΡΡΠ½ΠΊΡΠΈΡΠΌ. ΠΠ΅ΠΊΠΎΡΠΎΡΡΠ΅ Π±ΠΈΠ±Π»ΠΈΠΎΡΠ΅ΠΊΠΈ ΠΈΠΌΠ΅ΡΡ ΡΠΏΠ΅ΡΠΈΡΠΈΡΠ½ΡΠ΅ ΡΡΠ½ΠΊΡΠΈΠΈ, ΠΊΠΎΡΠΎΡΡΠ΅ Π΄Π»Ρ ΡΠ²ΠΎΠ΅ΠΉ ΡΠ°Π±ΠΎΡΡ ΡΡΠ΅Π±ΡΡΡ ΠΏΠ΅ΡΠ²ΠΎΠ½Π°ΡΠ°Π»ΡΠ½ΡΡ ΠΈΠ½ΠΈΡΠΈΠ°Π»ΠΈΠ·Π°ΡΠΈΡ. ΠΠ°ΠΊ ΠΏΡΠΈΠΌΠ΅Ρ: ΠΏΠΎΠΈΡΠΊ ΠΏΠΎΠ΄ΠΊΠ»ΡΡΠ΅Π½Π½ΡΡ ΡΡΡΡΠΎΠΉΡΡΠ² ΠΈ ΠΏΠΎΠ»ΡΡΠ΅Π½ΠΈΠ΅ Π½Π° Π½ΠΈΡ ΡΡΡΠ»ΠΎΠΊ Π΄Π»Ρ Π΄Π°Π»ΡΠ½Π΅ΠΉΡΠ΅ΠΉ ΡΠ°Π±ΠΎΡΡ ΠΈΠ»ΠΈ ΡΡΠ½ΠΊΡΠΈΠΈ, ΠΊΠΎΡΠΎΡΡΠ΅ ΡΡΠ΅Π±ΡΡΡ ΠΈΠ½ΠΈΡΠΈΠ°Π»ΠΈΠ·Π°ΡΠΈΠΈ Π±ΠΎΠ»ΡΡΠΎΠ³ΠΎ ΠΊΠΎΠ»ΠΈΡΠ΅ΡΡΠ²Π° ΠΏΠ°ΠΌΡΡΠΈ. ΠΡΠ»Π΅Π΄ΡΡΠ²ΠΈΠ΅ ΡΡΠΎΠ³ΠΎ Π²ΠΎΠ·Π½ΠΈΠΊΠ°Π΅Ρ Π²ΠΎΠΏΡΠΎΡ - ΠΊΠ°ΠΊ Π»ΡΡΡΠ΅ ΡΠ΅Π°Π»ΠΈΠ·ΠΎΠ²Π°ΡΡ ΠΏΠΎΠΊΡΡΡΠΈΠ΅ ΡΠ½ΠΈΡ-ΡΠ΅ΡΡΠ°ΠΌΠΈ ΡΠΏΠ΅ΡΠΈΡΠΈΡΠ½ΡΡ ΠΎΠ±ΡΠ΅ΠΊΡΠΎΠ², ΠΊΠΎΡΠΎΡΡΠ΅ Π²Π½ΡΡΡΠΈ ΡΠ΅Π±Ρ ΠΈΠΌΠ΅ΡΡ ΡΡΠ½ΠΊΡΠΈΠΈ, ΡΡΠ΅Π±ΡΡΡΠΈΠ΅ ΡΠΏΠ΅ΡΠΈΠ°Π»ΡΠ½ΡΡ ΡΡΠ»ΠΎΠ²ΠΈΠΉ Π΄Π»Ρ ΡΠ²ΠΎΠ΅ΠΉ ΡΠ°Π±ΠΎΡΡ?
https://habr.com/ru/companies/megafon/articles/914372/
#c++ #gtest #google_testing_framework #mocking #unittesting #unittests
Ok. I am very bad at unit tests. I would like to create some. This is on #macos; we use #cmake for the most part, and the #gtest suite for tests, but I'm ok if I can only make something for #xcode
One issue I don't understand is: in Swift, if I want to use a substitute class for a system one (specifically, NEAppProxyFlow and its subclasses)... how do I handle that? Do I provide my own module "NetworkExtension" for the unit tests? Or something else?
We've been working toward deprecating GTest for our testing library in favor of our in-house JTest testing library. J3ML our 3D math library is the current target for rewriting our unit tests to utilize JTest.
Anyone here a #googletest #gtest contributor and willing to take a look at my PR? Boosts very welcome :3
Okay, so when using #gtest / #gmock / #googletest to write C++ unit tests for code that uses dependency injection, how the *hell* do go about mocking dependencies of a class under test without having to mock the dependency class' dependencies, and *those* class' dependencies, and so on until you've mocked every class in the dependency tree of the class under test?
"Interfaces" or "templates" are *not* valid answers, as they drive complexity into your non-test code purely to support testing!
En train de dΓ©couvrir le fonctionnement de la monnaie Δ1 via @monnaielibreoccitanie
Je me suis inscrit sur ΔTest afin de me familiariser quelqu'un pour me certifier?
Inscrit sous Tigre-Bleu
voici ma clef publique: 8dDufS4JUkW1yEf753ibamHsLR5GJKF9NL6cGnMbiygW
