diff options
| author | Abseil Team <absl-team@google.com> | 2021-02-02 21:00:14 (GMT) |
|---|---|---|
| committer | Dino Radaković <dinor@google.com> | 2021-02-05 18:40:45 (GMT) |
| commit | 8599d312ce4eaec0cf403b04f54d1d580edfea71 (patch) | |
| tree | ee62cceb97c44f24e0a18ddf120664cb131cf0c4 /docs | |
| parent | fd873f6d7d22e231a083a7fc570f95961c36e85c (diff) | |
| download | googletest-8599d312ce4eaec0cf403b04f54d1d580edfea71.zip googletest-8599d312ce4eaec0cf403b04f54d1d580edfea71.tar.gz googletest-8599d312ce4eaec0cf403b04f54d1d580edfea71.tar.bz2 | |
Googletest export
Fix terminal output formatting in advanced guide
PiperOrigin-RevId: 355233178
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/advanced.md | 51 |
1 files changed, 19 insertions, 32 deletions
diff --git a/docs/advanced.md b/docs/advanced.md index 7885772..91a4ec1 100644 --- a/docs/advanced.md +++ b/docs/advanced.md @@ -2224,38 +2224,25 @@ random seed and re-shuffle the tests in each iteration. googletest can use colors in its terminal output to make it easier to spot the important information: -<code> -...<br/> - <font color="green">[----------]</font><font color="black"> 1 test from - FooTest</font><br/> - <font color="green">[ RUN ]</font><font color="black"> - FooTest.DoesAbc</font><br/> - <font color="green">[ OK ]</font><font color="black"> - FooTest.DoesAbc </font><br/> - <font color="green">[----------]</font><font color="black"> - 2 tests from BarTest</font><br/> - <font color="green">[ RUN ]</font><font color="black"> - BarTest.HasXyzProperty </font><br/> - <font color="green">[ OK ]</font><font color="black"> - BarTest.HasXyzProperty</font><br/> - <font color="green">[ RUN ]</font><font color="black"> - BarTest.ReturnsTrueOnSuccess ... some error messages ...</font><br/> - <font color="red">[ FAILED ]</font><font color="black"> - BarTest.ReturnsTrueOnSuccess ...</font><br/> - <font color="green">[==========]</font><font color="black"> - 30 tests from 14 test suites ran.</font><br/> - <font color="green">[ PASSED ]</font><font color="black"> - 28 tests.</font><br/> - <font color="red">[ FAILED ]</font><font color="black"> - 2 tests, listed below:</font><br/> - <font color="red">[ FAILED ]</font><font color="black"> - BarTest.ReturnsTrueOnSuccess</font><br/> - <font color="red">[ FAILED ]</font><font color="black"> - AnotherTest.DoesXyz<br/> -<br/> - 2 FAILED TESTS - </font> -</code> +<pre>... +<font color="green">[----------]</font> 1 test from FooTest +<font color="green">[ RUN ]</font> FooTest.DoesAbc +<font color="green">[ OK ]</font> FooTest.DoesAbc +<font color="green">[----------]</font> 2 tests from BarTest +<font color="green">[ RUN ]</font> BarTest.HasXyzProperty +<font color="green">[ OK ]</font> BarTest.HasXyzProperty +<font color="green">[ RUN ]</font> BarTest.ReturnsTrueOnSuccess +... some error messages ... +<font color="red">[ FAILED ]</font> BarTest.ReturnsTrueOnSuccess +... +<font color="green">[==========]</font> 30 tests from 14 test suites ran. +<font color="green">[ PASSED ]</font> 28 tests. +<font color="red">[ FAILED ]</font> 2 tests, listed below: +<font color="red">[ FAILED ]</font> BarTest.ReturnsTrueOnSuccess +<font color="red">[ FAILED ]</font> AnotherTest.DoesXyz + + 2 FAILED TESTS +</pre> You can set the `GTEST_COLOR` environment variable or the `--gtest_color` command line flag to `yes`, `no`, or `auto` (the default) to enable colors, |