tree: 979f05034ecc7880f9ce282b1f8ea03e62913c91 [path history] [tgz]
  2. cast-linux.content_browsertests.filter
  3. chromeos.base_unittests.filter
  4. chromeos.mash.browser_tests.filter
  7. chromeos.media_unittests.filter
  8. chromeos.services_unittests.filter
  9. fuchsia.base_perftests.filter
  10. fuchsia.content_unittests.filter
  11. fuchsia.mojo_unittests.filter
  12. fuchsia.net_perftests.filter
  13. fuchsia.net_unittests.filter
  14. fuchsia.ui_base_unittests.filter
  15. mac_window_server_killers.browser_tests.filter
  19. OWNERS
  22. site_isolation_android.content_browsertests.filter
  23. webrtc.content_unittests.filter
  24. webrtc_functional.browser_tests.filter
  25. webui_polymer2_browser_tests.filter
  26. webui_polymer2_interactive_ui_tests.filter

Test filter files


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).

File syntax

Contents of test filter files follow the syntax below:

  • Empty lines are ignored.
  • Any text after ‘#’ on each line is treated as comments and ignored.
  • All other lines specify a single test name pattern.
    • Negative patterns: Patterns prefixed with the ‘-’ character specify tests to exclude from a test run.
    • Positive patterns: All other patterns specify tests to include in a test run.

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 [] 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:

# Get tests working w/ --site-per-process

# Get extension browsertests working w/ --site-per-process


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 \

Example test invocation (multiple filter files, separated by ‘;’):

$ out/dbg/content_browsertests \

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 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 third_party/WebKit/LayoutTests/FlagExpectations/README.txt.

Adding new test filter files

Please use the following conventions when naming the new file:

  • Please include the name of the test executable (e.g. content_browsertests).
  • Please use .filter suffix.
  • Feel free to add other relevant things into the file name (e.g. the mode the file applies to - for example site-per-process).

When adding a new filter file, you will need to:

  • Update //testing/buildbot/filters/
  • Add //testing/buildbot/filters:foo_filters to the appropriate test target.
  • Add '--test-launcher-filter-file=../../testing/buildbot/filters/foo.filter' to the desired test suite(s) in test_suites.pyl.
  • Run testing/buildbot/ to update .json files.