diff options
| author | phajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-05-12 06:48:46 +0000 |
|---|---|---|
| committer | phajdan.jr@chromium.org <phajdan.jr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-05-12 06:48:46 +0000 |
| commit | bc2e3f3dbcbd308f2efeca56a7e73e20376aafb3 (patch) | |
| tree | e516f01b2090e9494033925ac05824b18cac572e /chrome/chrome_common.gypi | |
| parent | bd1b93d983c6cbf8e32458bd36a3aadf7490a770 (diff) | |
| download | chromium_src-bc2e3f3dbcbd308f2efeca56a7e73e20376aafb3.zip chromium_src-bc2e3f3dbcbd308f2efeca56a7e73e20376aafb3.tar.gz chromium_src-bc2e3f3dbcbd308f2efeca56a7e73e20376aafb3.tar.bz2 | |
[TTF] [GTTF] Implement the FAILS_ prefix for tests.
After this change, the meaning of the prefixes is as follows:
- DISABLED_: the test is not run unless --gtest_also_run_disabled_tests
flag is used; should be used for tests that crash or exceed the time limit
- FLAKY_: for tests that behave intermittently, and don't crash nor time out
- FAILS_: for tests that fail consistently, but don't crash nor time out
The Testing Task Force aims to run as much tests as possible, to keep
the coverage high.
The Green Tree Task Force aims to fix the flaky tests because they are
unpredictable.
To satisfy both goals, we should differentiate between the two cases,
and that's why we have both the FLAKY_ and FAILS_ prefixes.
When a test crashes or exceeds time limit (even intermittently),
we have no choice other than disable it, and that's why we have DISABLED_
(and it's built-in the gtest framework anyway).
TEST=none
BUG=none
Review URL: http://codereview.chromium.org/2015013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@47011 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_common.gypi')
0 files changed, 0 insertions, 0 deletions