You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, this is a cool project, thanks for sharing it. (BTW, can you please add a license file so we know what the terms of usage are?)
I noticed a problem with Xcode in that after the first run of the tests (and discovering the Google tests which are added by runtime injection) it caches those suites and tests. If you add a second test to CounterTest.cpp:
Now if you run GoogleTestCase again in TestNavigator it will only run the Counter test case with the initial tests (InitialState and Increment). The only workaround I found is to close the project and re-open it in XCode which causes XCode to lose all the dynamic XCTest information so when you run the GoogleTestCase if will discover (and cache) the new tests. Needless to say this is utterly annoying as I have to re-open the project any time I add/remove/disable a test.
Are you aware of this issue and if yes, do you know of a better workaround/fix?
Thanks!
The text was updated successfully, but these errors were encountered:
First, this is a cool project, thanks for sharing it. (BTW, can you please add a license file so we know what the terms of usage are?)
I noticed a problem with Xcode in that after the first run of the tests (and discovering the Google tests which are added by runtime injection) it caches those suites and tests. If you add a second test to CounterTest.cpp:
TEST(Counter2, Decrement) {
Counter counter;
EXPECT_EQ(-1, counter.Decrement());
}
Now if you run GoogleTestCase again in TestNavigator it will only run the Counter test case with the initial tests (InitialState and Increment). The only workaround I found is to close the project and re-open it in XCode which causes XCode to lose all the dynamic XCTest information so when you run the GoogleTestCase if will discover (and cache) the new tests. Needless to say this is utterly annoying as I have to re-open the project any time I add/remove/disable a test.
Are you aware of this issue and if yes, do you know of a better workaround/fix?
Thanks!
The text was updated successfully, but these errors were encountered: