eaca2ebd4c
- Run format on the current expectations file to make it up to date. - It's a lot easier to read the failures when they are grouped by the bug. Change-Id: I333a0b237ccd405d204e47809eb7ab723824fddd No-Try: True Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/98241 Auto-Submit: Loko Kung <lokokung@google.com> Reviewed-by: Corentin Wallez <cwallez@chromium.org> Commit-Queue: Loko Kung <lokokung@google.com> |
||
---|---|---|
.. | ||
scripts | ||
webtests | ||
BUILD.gn | ||
README.md | ||
expectations.txt | ||
test_page.html | ||
test_runner.js | ||
worker_test_globs.txt |
README.md
Running the WebGPU CTS Locally with Chrome
Running the WebGPU CTS locally with Chrome requires a Chromium checkout.
Follow these instructions for checking out
and building Chrome. You'll also need to build the telemetry_gpu_integration_test
target.
At the root of a Chromium checkout, run:
./content/test/gpu/run_gpu_integration_test.py webgpu_cts --browser=exact --browser-executable=path/to/your/chrome-executable
If you don't want to build Chrome, you can still run the CTS, by passing the path to an existing Chrome executable to the --browser-executable
argument. You should still build the telemetry_gpu_integration_test
target to support all harness
functionality.
Useful command-line arguments:
-l
: List all tests that would be run.--test-filter
: Filter tests. Run--help
for more information.--help
: See more options.--passthrough --show-stdout
: Show browser output. See also--browser-logging-verbosity
.--extra-browser-args
: Pass extra args to the browser executable.--is-backend-validation
: Enable backend validation. TODO: rename this to--backend-validation
.