Test apk(s) and tests to run on Android are configurable on a per Android release basis by editing webview_cts_gcs_path.json
.
{ { "<Android dessert letter>": { "arch": { "<arch1>": { "filename": "<relative path to cts_archive_dir of cts zip>", "_origin": "<CTS zip download url>", "unzip_dir": "<relative path to work directory where cts should be unzipped to>" }, "<arch2>": { "filename": "<relative path to cts_archive_dir of cts zip>", "_origin": "<CTS zip download url>", "unzip_dir": "<relative path to work directory where cts should be unzipped to>" } }, "test_runs": [ { "apk": "location of the test apk in the cts zip file", "excludes": [ { "match": "<class#testcase (wildcard supported) expression of test to skip>", "_bug_id": "<bug reference comment, optional>" } ] }, { "apk": "location of the test apk in the cts zip file", "includes": [ { "match": "<class#testcase (wildcard supported) expression of test to run>" } ] } ] } }, ... }
Add entries to the excludes
list for the respective apk under test_runs
.
Before re-enabling tests, make sure it's actually safe to enable the test again.
aosp/oreo-cts-dev
.Re-enabling the test case is as simple as removing it from the excludes
for the relevant OS levels. Please verify this change by adding the android-webview-*
trybots (not enabled by default).