This directory contains files that list tests that are not yet ready to run in a particular mode. For example - the
cast-linux.content_browsertests.filter file lists tests that should be excluded when running
content_browsertests on the Cast device or bot (e.g. on 'Cast Linux).
Contents of test filter files follow the syntax below:
A test will be executed if and only if it matches any of the positive patterns but does not match any of the negative patterns (please see documentation of --gtest_filter for more details and examples).
Please see [https://crbug.com/587527] for discussion how “positive” and “negative” test patterns should be combined in presence of both the
--gtest_filter and the
--test-launcher-filter-file command line flags.
Example test filter file for excluding a set of tests:
# crbug.com/417518: Get tests working w/ --site-per-process -BrowserTest.OtherRedirectsDontForkProcess -ChromeRenderProcessHostTest.* -ReferrerPolicyTest.HttpsRedirect # crbug.com/448592: Get extension browsertests working w/ --site-per-process -IsolatedAppTest.CookieIsolation -IsolatedAppTest.CrossProcessClientRedirect -IsolatedAppTest.IsolatedAppProcessModel -IsolatedAppTest.SubresourceCookieIsolation
When running tests on desktop platforms, the test filter file can be specified using
--test-launcher-filter-file command line flag. Example test invocation (single filter file):
$ out/dbg/content_browsertests \ --test-launcher-filter-file=testing/buildbot/filters/foo.content_browsertests.filter
Example test invocation (multiple filter files, separated by ‘;’):
$ out/dbg/content_browsertests \ --test-launcher-filter-file=testing/buildbot/filters/foo.content_browsertests.filter;\ testing/buildbot/filters/foo.chromeos.content_browsertests.filter
When running tests on Android, the test filter file can also be specified using
--test-launcher-filter-file command line flag. Example test invocation:
$ out/android/bin/run_content_browsertests \ --test-launcher-filter-file=testing/buildbot/filters/foo.content_browsertests.filter
Test filter files described here are currently only supported for gtest-based tests.
For excluding layout tests when running with a particular command line flag, see
Please use the following conventions when naming the new file:
When adding a new filter file, you will need to:
//testing/buildbot/filters:foo_filtersto the appropriate test target.
'--test-launcher-filter-file=../../testing/buildbot/filters/foo.filter'to the desired test suite(s) in
testing/buildbot/generate_buildbot_json.pyto update .json files.