diff options
| author | Abseil Team <absl-team@google.com> | 2020-04-10 21:45:24 (GMT) |
|---|---|---|
| committer | Mark Barolak <mbar@google.com> | 2020-04-16 17:32:42 (GMT) |
| commit | 373d72b6986fb9e5c364a0f5ceec22693415773f (patch) | |
| tree | 792b48a601cfd6b36b67b9b2379d222eacfd9e24 /googlemock/docs | |
| parent | 4fe5ac53337efd3534591929317c49f4018917ee (diff) | |
| download | googletest-373d72b6986fb9e5c364a0f5ceec22693415773f.zip googletest-373d72b6986fb9e5c364a0f5ceec22693415773f.tar.gz googletest-373d72b6986fb9e5c364a0f5ceec22693415773f.tar.bz2 | |
Googletest export
Fix link to "After clause". Sorry, reader, but this heading is in another document!
PiperOrigin-RevId: 305947971
Diffstat (limited to 'googlemock/docs')
| -rw-r--r-- | googlemock/docs/cook_book.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/googlemock/docs/cook_book.md b/googlemock/docs/cook_book.md index 51eb94a..4dbfbe0 100644 --- a/googlemock/docs/cook_book.md +++ b/googlemock/docs/cook_book.md @@ -1712,8 +1712,8 @@ brittle tests. For example, we may care about `A` occurring before both `B` and the test should reflect our real intent, instead of being overly constraining. gMock allows you to impose an arbitrary DAG (directed acyclic graph) on the -calls. One way to express the DAG is to use the [After](#AfterClause) clause of -`EXPECT_CALL`. +calls. One way to express the DAG is to use the +[After](cheat_sheet.md#AfterClause) clause of `EXPECT_CALL`. Another way is via the `InSequence()` clause (not the same as the `InSequence` class), which we borrowed from jMock 2. It's less flexible than `After()`, but |