Skip to content

G
googletest
Commit adeef192 by krzysio Committed by Gennadiy Rozental
Options

Googletest export

Mention matchers as an alternative to assertions in subroutines. Matchers are often the better choice - they can provide more informative error messages and circumvent all of the complexity described in this section. PiperOrigin-RevId: 326332149
parent 10ade847
Showing with 6 additions and 0 deletions
googletest/docs/advanced.md
...@@ -911,6 +911,12 @@ handlers registered with `pthread_atfork(3)`. ...@@ -911,6 +911,12 @@ handlers registered with `pthread_atfork(3)`.
## Using Assertions in Sub-routines ## Using Assertions in Sub-routines
Note: If you want to put a series of test assertions in a subroutine to check
for a complex condition, consider using
[a custom GMock matcher](../../googlemock/docs/cook_book.md#NewMatchers)
instead. This lets you provide a more readable error message in case of failure
and avoid all of the issues described below.
### Adding Traces to Assertions ### Adding Traces to Assertions
If a test sub-routine is called from several places, when an assertion inside it If a test sub-routine is called from several places, when an assertion inside it
......
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