Lines Matching refs:fixture

92 *test fixture* class.
208 can use a *test fixture*. This allows you to reuse the same configuration of
211 To create a fixture:
214     we'll want to access fixture members from sub-classes.
226 When using a fixture, use `TEST_F()` instead of `TEST()` as it allows you to
227 access objects and subroutines in the test fixture:
236 fixture class. (`_F` stands for "Fixture"). No test suite name is specified for
243 Also, you must first define a test fixture class before using it in a
248 fixture at runtime, immediately initialize it via `SetUp()`, run the test, clean
249 up by calling `TearDown()`, and then delete the test fixture. Note that
250 different tests in the same test suite have different test fixture objects, and
251 GoogleTest always deletes a test fixture before it creates the next one.
252 GoogleTest does **not** reuse the same test fixture for multiple tests. Any
253 changes one test makes to the fixture do not affect other tests.
270 First, define a fixture class. By convention, you should give it the name
295 Now we'll write tests using `TEST_F()` and this fixture.
352 *   Creates a test fixture object for the first test.
356 *   Runs the test on the fixture object.
358 *   Cleans up the fixture via `TearDown()`.
360 *   Deletes the fixture.
403 // The fixture for testing class Foo.