I recently deployed a change to make isolated tests + webkit layout tests produce the following text output. This makes it much clearer what tests ran, what is failing, etc.
We should make gtest and everything else also output the *same* text -- IE everything should look the same to the developer.
There are a couple of extra states which the current output doesn't handle. They are;
* Number of disabled tests.
* Number of skipped tests.
b
Also when https://bugs.chromium.org/p/chromium/issues/detail?id=704387 is fixed. This text output can be even more human friendly.
================================================
On success;
-------
Total tests: 6
* Passed: 1 (1 expected, 0 unexpected)
* Failed: 2 (2 expected, 0 unexpected)
* Flaky: 3 (3 expected, 0 unexpected)
-------
On the failure case;
-------
Total tests: 6
* Passed: 1 (1 expected, 0 unexpected)
* Failed: 2 (0 expected, >>>2 unexpected<<<)
* Flaky: 3 (3 expected, 0 unexpected)
Unexpected Failures:
* bad/totally-bad-probably.html
* tricky/totally-maybe-not-awesome.html
-------
It also trims if there are too many failures;
-------
Total tests: 131
* Passed: 1 (1 expected, 0 unexpected)
* Failed: 127 (0 expected, >>>127 unexpected<<<)
* Flaky: 3 (0 expected, >>>3 unexpected<<<)
Unexpected Failures:
* bad/failing0.html
<snip>
* bad/failing27.html
* bad/failing28.html
* bad/failing29.html
* ... 97 more ...
Unexpected Flakes:
* flake/slow.html
* flake/timeout-then-crash.html
* flake/totally-flakey.html
-------
I recently deployed a change to make isolated tests + webkit layout tests produce the following text output. This makes it much clearer what tests ran, what is failing, etc.
We should make gtest and everything else also output the *same* text -- IE everything should look the same to the developer.
There are a couple of extra states which the current output doesn't handle. They are;
* Number of disabled tests.
* Number of skipped tests.
Also when https://bugs.chromium.org/p/chromium/issues/detail?id=704387 is fixed. This text output can be even more human friendly.
================================================
On success;
-------
Total tests: 6
* Passed: 1 (1 expected, 0 unexpected)
* Failed: 2 (2 expected, 0 unexpected)
* Flaky: 3 (3 expected, 0 unexpected)
-------
On the failure case;
-------
Total tests: 6
* Passed: 1 (1 expected, 0 unexpected)
* Failed: 2 (0 expected, >>>2 unexpected<<<)
* Flaky: 3 (3 expected, 0 unexpected)
Unexpected Failures:
* bad/totally-bad-probably.html
* tricky/totally-maybe-not-awesome.html
-------
It also trims if there are too many failures;
-------
Total tests: 131
* Passed: 1 (1 expected, 0 unexpected)
* Failed: 127 (0 expected, >>>127 unexpected<<<)
* Flaky: 3 (0 expected, >>>3 unexpected<<<)
Unexpected Failures:
* bad/failing0.html
<snip>
* bad/failing27.html
* bad/failing28.html
* bad/failing29.html
* ... 97 more ...
Unexpected Flakes:
* flake/slow.html
* flake/timeout-then-crash.html
* flake/totally-flakey.html
-------
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Comment 1 by jparent@chromium.org
, Mar 23 2017