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
Some users are confused when about the effect of test case instantiations
in value-parameterized test cases. For example, in this code:
TEST_P(FooTest, TestSomething) { .. }
INSTANTIATE_TEST_CASE_P(InstantiationA, FooTest, ...);
TEST_P(FooTest, TestSomethingElse) { ... }
INSTANTIATE_TEST_CASE_P(InstantiationB, FooTest, ...);
some people expect InstantiationA NOT to instantiate
FooTest.TestSomethingElse. We need to issue a warning when TEST_P follows
INSTANTIATE_TEST_CASE_P for the same test case.
Original issue reported on code.google.com by vladlosev on 12 Nov 2008 at 7:23
The text was updated successfully, but these errors were encountered:
More generally the instantiation macro for the Value-parameterized tests should
offer a mechanism to instantiate only a subset of defined TEST_P.
It could be for instante an optional parameter "pattern matching" the wanted
TEST_P, or an enumeration of TEST_P.
Currently I don't see any other solution than to derivate the
Value-parameterized fixture.
Original issue reported on code.google.com by
vladlosev
on 12 Nov 2008 at 7:23The text was updated successfully, but these errors were encountered: