diff options
| author | Wiktor Garbacz <wiktorg@google.com> | 2018-08-09 11:14:36 (GMT) |
|---|---|---|
| committer | Wiktor Garbacz <wiktorg@google.com> | 2018-08-09 11:14:36 (GMT) |
| commit | db43df6df733c3b6c8a0a049e2000bb9869c5a8a (patch) | |
| tree | 0e7c7fbbc2ba79f406305af500f0fa0a3c04cc8d /googletest/docs/faq.md | |
| parent | 4de57ce787989d821d0736c5a12188eeaea3bf2d (diff) | |
| download | googletest-db43df6df733c3b6c8a0a049e2000bb9869c5a8a.zip googletest-db43df6df733c3b6c8a0a049e2000bb9869c5a8a.tar.gz googletest-db43df6df733c3b6c8a0a049e2000bb9869c5a8a.tar.bz2 | |
docs: fix broken links
Diffstat (limited to 'googletest/docs/faq.md')
| -rw-r--r-- | googletest/docs/faq.md | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/googletest/docs/faq.md b/googletest/docs/faq.md index d613f7b..7d42ff7 100644 --- a/googletest/docs/faq.md +++ b/googletest/docs/faq.md @@ -707,8 +707,9 @@ In general, the recommended way to cause the code to behave differently under test is [Dependency Injection](https://en.wikipedia.org/wiki/Dependency_injection). You can inject different functionality from the test and from the production code. Since your production code doesn't link in the for-test logic at all (the -[`testonly`](http://go/testonly) attribute for BUILD targets helps to ensure -that), there is no danger in accidentally running it. +[`testonly`](https://docs.bazel.build/versions/master/be/common-definitions.html#common.testonly) +attribute for BUILD targets helps to ensure that), there is no danger in +accidentally running it. However, if you *really*, *really*, *really* have no choice, and if you follow the rule of ending your test program names with `_test`, you can use the |