organicmaps/googletest
13
Fork 0
mirror of https://github.com/google/googletest.git synced 2025-04-06 05:55:04 +00:00
Code Issues 1 Projects Releases Wiki Activity Actions

Adds instructions on accessing command line flags in code.

Browse source
This commit is contained in:
zhanyong.wan 2009-01-20 18:54:25 +00:00
parent 6629501806
commit deab401ff7
1 changed files with 17 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

19
wiki/GoogleTestAdvancedGuide.wiki
View file

@ -1330,8 +1330,23 @@ them directly and affect their behavior via the following environment variables
and/or command line flags. For the flags to work, your programs must call
`testing::InitGoogleTest()` before calling `RUN_ALL_TESTS()`.
If an option is specified both by an environment variable and by a flag, the
latter takes precedence.
If an option is specified both by an environment variable and by a
flag, the latter takes precedence. Most of the options can also be
set/read in code: to access the value of command line flag
`--gtest_foo`, write `testing::GTEST_FLAG(foo)`. A common pattern is
to set the value of a flag before calling `testing::InitGoogleTest()`
to change the default value of the flag:
{{{
int main(int argc, char** argv) {
// Prints elapsed time by default.
testing::GTEST_FLAG(print_time) = true;
// This allows the user to override the flag on the command line.
testing::InitGoogleTest(&argc, argv);
return RUN_ALL_TESTS();
}
}}}
== Turning Assertion Failures into Break-Points ==