gitMirror/googletest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Docs: add conditions for calling TearDown()

Browse Source
This commit is contained in:
kaswhy 2023-12-29 02:05:18 +09:00
parent dddb219c3e
commit dda72ef321
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/advanced.md
View File

@ -1006,9 +1006,12 @@ Environment* AddGlobalTestEnvironment(Environment* env);
Now, when `RUN_ALL_TESTS()` is called, it first calls the `SetUp()` method of Now, when `RUN_ALL_TESTS()` is called, it first calls the `SetUp()` method of
each environment object, then runs the tests if none of the environments each environment object, then runs the tests if none of the environments
reported fatal failures and `GTEST_SKIP()` was not called. `RUN_ALL_TESTS()` reported fatal failures and `GTEST_SKIP()` was not called.
always calls `TearDown()` with each environment object, regardless of whether or
not the tests were run. RUN_ALL_TESTS() calls TearDown() for each environment object when they are recreated
for each iteration. However, if the test environments are not recreated for each iteration,
TearDown() is called only on the last iteration.
Additionally, TearDown() is executed regardless of whether the tests were run or not.
It's OK to register multiple environment objects. In this suite, their `SetUp()` It's OK to register multiple environment objects. In this suite, their `SetUp()`
will be called in the order they are registered, and their `TearDown()` will be will be called in the order they are registered, and their `TearDown()` will be