summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAbseil Team <absl-team@google.com>2021-03-24 18:20:36 -0700
committerDino Radaković <dinor@google.com>2021-03-25 13:43:36 -0700
commit66836f0a906dcac04d19febc86ef942e52d331eb (patch)
tree8f7698f29532876fd77cbcdae9453b4904e87591
parent6dabd081e948f58d50322f103915998bb84d46a1 (diff)
downloadgoogletest-66836f0a906dcac04d19febc86ef942e52d331eb.tar.gz
googletest-66836f0a906dcac04d19febc86ef942e52d331eb.zip
Googletest export
Minor formatting updates PiperOrigin-RevId: 364935205
-rw-r--r--docs/faq.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/faq.md b/docs/faq.md
index 1b6d8b6d..40712321 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -706,12 +706,12 @@ whether the code is under test.
## How do I temporarily disable a test?
If you have a broken test that you cannot fix right away, you can add the
-DISABLED_ prefix to its name. This will exclude it from execution. This is
-better than commenting out the code or using #if 0, as disabled tests are still
-compiled (and thus won't rot).
+`DISABLED_` prefix to its name. This will exclude it from execution. This is
+better than commenting out the code or using `#if 0`, as disabled tests are
+still compiled (and thus won't rot).
To include disabled tests in test execution, just invoke the test program with
-the --gtest_also_run_disabled_tests flag.
+the `--gtest_also_run_disabled_tests` flag.
## Is it OK if I have two separate `TEST(Foo, Bar)` test methods defined in different namespaces?
OpenPOWER on IntegriCloud