summaryrefslogtreecommitdiffstats
path: root/googletest
diff options
context:
space:
mode:
authorGennadiy Civil <misterg@google.com>2019-07-18 15:39:49 (GMT)
committerGennadiy Civil <misterg@google.com>2019-07-18 15:39:49 (GMT)
commit15756aa0c88591c10108e740ad3096a3af966242 (patch)
treefd3074818b6a3b3c594fd2ac0760ed72277900a5 /googletest
parent34ddfff9469cba9944ba0159beca02fb42321465 (diff)
downloadgoogletest-15756aa0c88591c10108e740ad3096a3af966242.zip
googletest-15756aa0c88591c10108e740ad3096a3af966242.tar.gz
googletest-15756aa0c88591c10108e740ad3096a3af966242.tar.bz2
Manual docs tweaks still in preparation for including docs with code pushes
Diffstat (limited to 'googletest')
-rw-r--r--googletest/docs/faq.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/googletest/docs/faq.md b/googletest/docs/faq.md
index a22f1b9..0e9cfee 100644
--- a/googletest/docs/faq.md
+++ b/googletest/docs/faq.md
@@ -332,7 +332,7 @@ You may still want to use `SetUp()/TearDown()` in the following cases:
* In the body of a constructor (or destructor), it's not possible to use the
`ASSERT_xx` macros. Therefore, if the set-up operation could cause a fatal
test failure that should prevent the test from running, it's necessary to
- use `abort` <!-- GOOGLETEST_CM0014 DO NOT DELETE --> and abort the whole test executable,
+ use `abort` <!-- GOOGLETEST_CM0015 DO NOT DELETE --> and abort the whole test executable,
or to use `SetUp()` instead of a constructor.
* If the tear-down operation could throw an exception, you must use
`TearDown()` as opposed to the destructor, as throwing in a destructor leads