summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAbseil Team <absl-team@google.com>2021-06-08 23:22:46 (GMT)
committerDerek Mauro <dmauro@google.com>2021-06-09 12:45:11 (GMT)
commit94bb786f0e51dcda7e0b91ffe53297a0eec5b9c5 (patch)
treedd3962d1af2d7175d442222e0d74deee2b19e852
parent5bcd8e3bb929714e031a542d303f818e5a5af45d (diff)
downloadgoogletest-94bb786f0e51dcda7e0b91ffe53297a0eec5b9c5.zip
googletest-94bb786f0e51dcda7e0b91ffe53297a0eec5b9c5.tar.gz
googletest-94bb786f0e51dcda7e0b91ffe53297a0eec5b9c5.tar.bz2
Googletest export
Update broken link PiperOrigin-RevId: 378272186
-rw-r--r--docs/gmock_faq.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/gmock_faq.md b/docs/gmock_faq.md
index 09623b4..2cd9b3f 100644
--- a/docs/gmock_faq.md
+++ b/docs/gmock_faq.md
@@ -87,9 +87,9 @@ trace, you'll gain insights on why the expectations you set are not met.
If you see the message "The mock function has no default action set, and its
return type has no default value set.", then try
-[adding a default action](gmock_for_dummies.md#DefaultValue). Due to a known
-issue, unexpected calls on mocks without default actions don't print out a
-detailed comparison between the actual arguments and the expected arguments.
+[adding a default action](gmock_cheat_sheet.md#OnCall). Due to a known issue,
+unexpected calls on mocks without default actions don't print out a detailed
+comparison between the actual arguments and the expected arguments.
### My program crashed and `ScopedMockLog` spit out tons of messages. Is it a gMock bug?