From 8f781fd214bd26ae6c3461c3cdce581b810b2cc4 Mon Sep 17 00:00:00 2001 From: shiqian Date: Tue, 26 Aug 2008 18:28:23 +0000 Subject: [PATCH] Edited wiki page through web user interface. --- wiki/GoogleTestAdvancedGuide.wiki | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/wiki/GoogleTestAdvancedGuide.wiki b/wiki/GoogleTestAdvancedGuide.wiki index 9c4e98729..dfd9ee9f9 100644 --- a/wiki/GoogleTestAdvancedGuide.wiki +++ b/wiki/GoogleTestAdvancedGuide.wiki @@ -1100,8 +1100,10 @@ you a chance to debug. Here's how to use it: || `$ foo_test --gtest_repeat=1000 --gtest_break_on_failure` || Repeat foo_test 1000 times, stopping at the first failure. This is especially useful when running under a debugger: when the testfails, it will drop into the debugger and you can then inspect variables and stacks. || || `$ foo_test --gtest_repeat=1000 --gtest_filter=FooBar` || Repeat the tests whose name matches the filter 1000 times. || -You can also specify the repeat count by setting the `GTEST_REPEAT` environment -variable. +If your test program contains global set-up/tear-down code registered +using `AddGlobalTestEnvironment()`, it will be repeated in each +iteration as well, as the flakiness may be in it. You can also specify +the repeat count by setting the `GTEST_REPEAT` environment variable. _Availability:_ Linux, Windows, Mac.