Lines Matching refs:death

131 ## My death test modifies some state, but the change seems lost after the death test finishes. Why?
139 In particular, if you use mocking and the death test statement invokes some mock
258 ## My death test hangs (or seg-faults). How do I fix it?
260 In GoogleTest, death tests are run in a child process and the way they work is
261 delicate. To write death tests you really need to understand how they work—see
262 the details at [Death Assertions](reference/assertions.md#death) in the
265 In particular, death tests don't like having multiple threads in the parent
274 leaving as few things as possible in it. Also, you can try to set the death test
277 If you go with thread-safe death tests, remember that they rerun the test
453 `ASSERT_DEATH(statement, matcher)` (or any death assertion macro) can be used
465 // A death test can be a simple function call.
487 // A death assertion can contain a compound statement.
521 means you cannot safely run a death test.
552 …calling my entire test suite `*DeathTest` when it contains both death tests and non-death tests. W…
570 …ints the LOG messages in a death test's child process only when the test fails. How can I see the …
574 GoogleTest only prints them when the death test has failed.
577 break the death test (e.g. by changing the regex pattern it is expected to
579 after the fork-and-exec-style death tests are implemented.