README.txt 1.0 KB

1234567891011121314151617181920212223242526272829
  1. web_tests/FlagExpectations stores flag-specific test expectations.
  2. Please see [1] for details, and see [2] to see if a flag-specific test
  3. configuration is suitable for you.
  4. To run layout tests with a flag passed to content_shell, use:
  5. run_web_tests.py --flag-specific=config-name
  6. It requires web_tests/FlagSpecificConfig to contain an entry for "config-name",
  7. e.g.:
  8. {
  9. "name": "config-name",
  10. "args": ["--flag1", "--flag2"]
  11. }
  12. run_web_tests.py will pass "--flag1 --flag2" to content_shell.
  13. You can create a new file:
  14. FlagExpectations/config-name
  15. The entries in the file is the same as the main TestExpectations file, e.g.
  16. crbug.com/123456 path/to/your/test.html [ Expectation ]
  17. This file will override the main TestExpectations file when the above command
  18. is run.
  19. [1] https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_tests.md#flag_specific-or-additional_driver_flag
  20. [2] https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_tests.md#Choosing-between-flag_specific-and-virtual-test-suite