3party/googletest
0
0
Fork 0
mirror of https://github.com/google/googletest.git synced 2024-12-26 17:41:03 +08:00
Code Issues Projects Releases Wiki Activity

Googletest export

Browse Source 
Fix documentation. This address https://github.com/google/googletest/pull/2827.

PiperOrigin-RevId: 309241571
This commit is contained in:
Abseil Team 2020-04-30 12:34:43 -04:00 committed by Gennadiy Rozental
parent 3cfb4117f7
commit 0eea2e9fc6
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
googletest/docs/advanced.md
View File

@ -1776,7 +1776,7 @@ In frameworks that report a failure by throwing an exception, you could catch
the exception and assert on it. But googletest doesn't use exceptions, so how do
we test that a piece of code generates an expected failure?
gunit-spi.h contains some constructs to do this. After #including this header,
`"gtest/gtest-spi.h"` contains some constructs to do this. After #including this header,
you can use
```c++
@ -1924,8 +1924,8 @@ To obtain a `TestInfo` object for the currently running test, call
```
`current_test_info()` returns a null pointer if no test is running. In
particular, you cannot find the test suite name in `TestSuiteSetUp()`,
`TestSuiteTearDown()` (where you know the test suite name implicitly), or
particular, you cannot find the test suite name in `SetUpTestSuite()`,
`TearDownTestSuite()` (where you know the test suite name implicitly), or
functions called from them.
## Extending googletest by Handling Test Events