Lines Matching refs:TearDown
250 void TearDown() override {
252 BaseTest::TearDown(); // Remember to tear down the base fixture
306 ## Should I use the constructor/destructor of the test fixture or SetUp()/TearDown()? {#CtorVsSetUp}
311 call `TearDown()`, and then delete the test fixture object.
314 between using the test fixture constructor/destructor or `SetUp()/TearDown()`.
323 *afterward*. With `SetUp()/TearDown()`, a subclass may make the mistake of
324 forgetting to call the base class' `SetUp()/TearDown()` or call them at the
327 You may still want to use `SetUp()/TearDown()` in the following cases:
336 `SetUp()/TearDown()`.
343 `TearDown()` as opposed to the destructor, as throwing in a destructor leads
346 enabled in the compiler. Therefore you should prefer `TearDown()` if you