e1bcb0b416
• Add `intel-hd-630-family` to the list of GPU tags (crbug.com/dawn/1444). • `[ Skip ]` all the `inputSource="const"` expression tests for now (crbug.com/tint/1613). • Reorder / normalize the rest of the expectations with `./tools/run cts update`. Bug: dawn:1444 Bug: tint:1613 Change-Id: I39efc454ecff6e804417bcade744a4251acbda07 Reviewed-on: https://dawn-review.googlesource.com/c/dawn/+/95842 Reviewed-by: Austin Eng <enga@chromium.org> Auto-Submit: Ben Clayton <bclayton@google.com> Kokoro: Kokoro <noreply+kokoro@google.com> Commit-Queue: Ben Clayton <bclayton@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
.