Lines Matching full:fixture

241 a method of the test fixture class. The one constraint is that assertions that
295     GTEST_SKIP() << "Skipping all tests for this fixture";
488 If a test fixture class is shared by normal tests and death tests, you can use
489 `using` or `typedef` to introduce an alias for the fixture class and avoid
838 fixture, you must add the `::testing::Test::` prefix, as in:
876 >     `TEST` body and the test fixture class.
889 GoogleTest creates a new test fixture object for each test in order to make
898 1.  In your test fixture class (say `FooTest` ), declare as `static` some member
900 2.  Outside your test fixture class (typically just below it), define those
902 3.  In the same test fixture class, define a public member function `static void
918 Note that `SetUpTestSuite()` may be called multiple times for a test fixture
1063 To write value-parameterized tests, first you should define a fixture class. It
1066 values. For convenience, you can just derive the fixture class from
1073 NOTE: If your test fixture defines `SetUpTestSuite()` or `TearDownTestSuite()`
1080   // You can implement all the usual fixture class members here.
1085 // Or, when you want to add parameters to a pre-existing fixture class:
1095 Then, use the `TEST_P` macro to define as many test patterns using this fixture
1205 1.  Put the definition of the parameterized test fixture class (e.g. `FooTest`)
1288 First, define a fixture class template. It should be parameterized by a type.
1324   // To visit static members of the fixture, add the 'TestFixture::'
1328   // To refer to typedefs in the fixture, add the 'typename TestFixture::'
1357 First, define a fixture class template, as we did with typed tests:
1381   // You will need to use `this` explicitly to refer to fixture members.
1459     fixture as a friend to the class and define accessors in your fixture. Tests
1460     using the fixture can then access the private members of your production
1461     class via the accessors in the fixture. Note that even though your fixture
1464     fixture.
1606 ownership to the caller. The signature of the callable is `Fixture*()`, where
1607 `Fixture` is the test fixture class for the test. All tests registered with the
1608 same `test_suite_name` must return the same fixture type. This is checked at
1611 The framework will infer the fixture class from the factory and will call the
1644         // Important to use the fixture type as the return type here.
1661 For example, you may be using the `SetUp()` method of your test fixture to set