gecko-dev/testing/web-platform/tests/docs/running-tests/chrome_android.md
Robert Ma ef1dbe597e Bug 1570756 [wpt PR 18239] - [tools] Various Chrome for Android improvements, a=testonly
Automatic update from web-platform-tests
[wpt] Support detecting Chrome for Android version

Consequently, we can now install the correct ChromeDriver version.

* The change also includes some drive-by whitespace fixes in the file.

--
Allow custom package names for Chrome Android

1. [wptrunner] chrome_android now honours (and requires) the
   --package-name flag instead of hardcoding the package name.
2. [wpt] chrome_android now chooses the correct official package name
   depending on the channel.
3. [wpt] chrome_android correctly sets browser_version.
4. [wpt] drive-by change: update the logic for adding --binary-arg &
   --webdriver-arg in chrome & chrome_android (now they both add
   --enable-experimental... to binary_arg and --disable-build-check to
   webdriver_arg when running dev or canary channel).

--

wpt-commits: cc864ad313dafdaefa90b483818ed5a603803a41, 2a4e78b2c66b7a6589c50c44dda31e5cf215421f
wpt-pr: 18239
2019-08-07 13:18:32 +00:00

851 B

Chrome for Android

To run WPT on Chrome on an Android device, some additional set up is required.

As with usual Android development, you need to have adb and be able to connect to the device. Run adb devices to verify.

Currently, Android support is a prototype with some known issues:

  • If you have previously run ./wpt run against Chrome, you might need to remove _venv/bin/chromedriver so that we can install the correct ChromeDriver corresponding to your Chrome for Android version.
  • We do not support reftests at the moment.
  • You will need to manually kill Chrome (all channels) before running tests.

Note: rooting the device or installing a root CA is no longer required.

Example (assuming you have Chrome Canary installed on your phone):

./wpt run --test-type=testharness --channel=canary chrome_android TESTS