Lines Matching full:tests
33 // implementations of the same interface (aka interface tests).
69 // for keeping the tests close to the real world scenario, where the
81 // Google Test offers two ways for reusing tests for different types.
82 // The first is called "typed tests". You should use it if you
84 // the tests.
145 // to test when you write the tests. For example, if you are the
147 // might want to write a set of tests to make sure each implementation
151 // How can you write the tests without committing to the type
152 // parameters? That's what "type-parameterized tests" can do for you.
153 // It is a bit more involved than typed tests, but in return you get a
198 // Type-parameterized tests involve one extra step: you have to
199 // enumerate the tests you defined:
207 // the tests with.
209 // To turn the abstract test pattern into real tests, you instantiate
