Add explanation on when/how to request resources for additional tests
As there would be such request often, add this to document. Bug: None Change-Id: Ife2b0705448526b3fccd4f445325bbd3f4c1fe82 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6333678 Commit-Queue: Weizhong Xia <weizhong@google.com> Reviewed-by: Jonathan Lee <jonathanjlee@google.com> Cr-Commit-Position: refs/heads/main@{#1429243}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
f0559b9760
commit
5b6338c45b
@ -102,7 +102,9 @@ The builder `android-chrome-13-x64-wpt-android-specific` and
|
||||
`android-webview-13-x64-wpt-android-specific` builders run tests specified by
|
||||
the [`android.filter`](/third_party/blink/web_tests/TestLists/android.filter)
|
||||
file, which tests Android-specific behaviors. Developers can add additional
|
||||
tests to the list when necessary.
|
||||
tests to the list when necessary. A resource request might be
|
||||
needed depending on the case. See [below](#Run-more-tests-with-Chrome-Android-or-WebView)
|
||||
for details.
|
||||
|
||||
To satisfy different testing requirements, WPT coverage in CQ/CI is partitioned
|
||||
between suites that target different `//content` embedders:
|
||||
@ -135,6 +137,20 @@ To update baselines:
|
||||
2. Run [the rebaseline tool](./web_test_expectations.md#How-to-rebaseline) after
|
||||
the results are ready.
|
||||
|
||||
## Run more tests with Chrome Android or WebView
|
||||
|
||||
A resource request would be needed if running the additional tests increases the
|
||||
total test time by more than one minute. If this is the case, developers can use
|
||||
[the bot estimator](https://data.corp.google.com/sites/datasite_browser_infra/bot_estimator?p=task_type:%22test%22)
|
||||
to estimate the bots needed, then follow the steps at [go/i-need-hw](https://g3doc.corp.google.com/company/teams/chrome/ops/business/resources/resource-request-program.md?cl=head&polyglot=physical-hw#i-need-new-resources)
|
||||
to get the resources. The tests can be added to the filter file after the resource
|
||||
is deployed.
|
||||
|
||||
Please make sure there is no unexpected failures on the related steps before using
|
||||
the bot estimator, as the bot will retry those tests and that will increase the
|
||||
total test time. For tests not intended to run with a target, e.g. WebView, you
|
||||
can skip the tests by adding "Skip" test expectations to [MobileTestExpectations](/third_party/blink/web_tests/MobileTestExpectations).
|
||||
|
||||
## Known Issues
|
||||
|
||||
For runner bugs and feature requests, please file [an issue against
|
||||
|
Reference in New Issue
Block a user