Skip to content

G
googletest
Commit 0eea2e9f by Abseil Team Committed by Gennadiy Rozental
Options

Googletest export

Fix documentation. This address https://github.com/google/googletest/pull/2827. PiperOrigin-RevId: 309241571
parent 3cfb4117
Showing with 3 additions and 3 deletions
googletest/docs/advanced.md
...@@ -1776,7 +1776,7 @@ In frameworks that report a failure by throwing an exception, you could catch ...@@ -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 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? 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 you can use
```c++ ```c++
...@@ -1924,8 +1924,8 @@ To obtain a `TestInfo` object for the currently running test, call ...@@ -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 `current_test_info()` returns a null pointer if no test is running. In
particular, you cannot find the test suite name in `TestSuiteSetUp()`, particular, you cannot find the test suite name in `SetUpTestSuite()`,
`TestSuiteTearDown()` (where you know the test suite name implicitly), or `TearDownTestSuite()` (where you know the test suite name implicitly), or
functions called from them. functions called from them.
## Extending googletest by Handling Test Events ## Extending googletest by Handling Test Events
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment