Skip to content

GitLab

"docs/advanced.md" did not exist on "a743249a5534eb57d3f5b4b0bb6d51b8dd2d5c68"
Commit d966d5fb authored by Gennadiy Civil's avatar Gennadiy Civil Committed by GitHub
Browse files

Merge pull request #968 from nicolacavallini/link_typed_test_docs 

added link to sample 6 in the  documentation of typed test
parents e2e37c94 2eaab215
Hide whitespace changes
Inline Side-by-side
Showing with 2 additions and 2 deletions
googletest/docs/AdvancedGuide.md
View file @ d966d5fb
...@@ -1344,7 +1344,7 @@ TYPED_TEST(FooTest, DoesBlah) { ...@@ -1344,7 +1344,7 @@ TYPED_TEST(FooTest, DoesBlah) {
TYPED_TEST(FooTest, HasPropertyA) { ... } TYPED_TEST(FooTest, HasPropertyA) { ... }
``` ```
You can see `samples/sample6_unittest.cc` for a complete example. You can see [`samples/sample6_unittest.cc`](../samples/sample6_unittest.cc) for a complete example.
_Availability:_ Linux, Windows (requires MSVC 8.0 or above), Mac; _Availability:_ Linux, Windows (requires MSVC 8.0 or above), Mac;
since version 1.1.0. since version 1.1.0.
...@@ -1551,7 +1551,7 @@ exception, you could catch the exception and assert on it. But Google ...@@ -1551,7 +1551,7 @@ exception, you could catch the exception and assert on it. But Google
Test doesn't use exceptions, so how do we test that a piece of code Test doesn't use exceptions, so how do we test that a piece of code
generates an expected failure? generates an expected failure?
`"gtest/gtest-spi.h"` contains some constructs to do this. After `"gtest/gtest-spi.h"` contains some constructs to do this. After
`#include`ing this header, you can use `#include`ing this header, you can use
| `EXPECT_FATAL_FAILURE(`_statement, substring_`);` | | `EXPECT_FATAL_FAILURE(`_statement, substring_`);` |
......
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