Lines Matching refs:TearDown

229   void TearDown() override {
231     BaseTest::TearDown();  // Remember to tear down the base fixture
285 ## Should I use the constructor/destructor of the test fixture or SetUp()/TearDown()? {#CtorVsSetUp}
290 call `TearDown()`, and then delete the test fixture object.
293 between using the test fixture constructor/destructor or `SetUp()`/`TearDown()`.
302     *afterward*. With `SetUp()/TearDown()`, a subclass may make the mistake of
303     forgetting to call the base class' `SetUp()/TearDown()` or call them at the
306 You may still want to use `SetUp()/TearDown()` in the following cases:
315     `SetUp()/TearDown()`.
322     `TearDown()` as opposed to the destructor, as throwing in a destructor leads
325     enabled in the compiler. Therefore you should prefer `TearDown()` if you