Bug 1449889 [wpt PR 10238] - Document useful arguments for `wpt run chrome`, a=testonly
authorPhilip Jägenstedt <philip@foolip.org>
Mon, 09 Apr 2018 22:03:17 +0000
changeset 413734 880bb3f3bd3a6edc38e9e15be3230523b107a3dc
parent 413733 a31ec4bc13acf088bed00900b397699376b13853
child 413735 06e258ea8af70189d18e9504be0183b298e5e6af
push id33850
push userapavel@mozilla.com
push dateMon, 16 Apr 2018 09:53:48 +0000
treeherdermozilla-central@6276ec7ebbf3 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerstestonly
bugs1449889, 10238
milestone61.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1449889 [wpt PR 10238] - Document useful arguments for `wpt run chrome`, a=testonly Automatic update from web-platform-testsDocument useful arguments for `wpt run chrome` (#10238) wpt-commits: 162e9dda47d694596620b69c5fb23cc7f0f87126 wpt-pr: 10238 wpt-commits: 162e9dda47d694596620b69c5fb23cc7f0f87126 wpt-pr: 10238
testing/web-platform/meta/MANIFEST.json
testing/web-platform/tests/docs/_running-tests/chrome.md
testing/web-platform/tests/docs/_running-tests/index.md
--- a/testing/web-platform/meta/MANIFEST.json
+++ b/testing/web-platform/meta/MANIFEST.json
@@ -269724,16 +269724,21 @@
      {}
     ]
    ],
    "docs/_reviewing-tests/index.md": [
     [
      {}
     ]
    ],
+   "docs/_running-tests/chrome.md": [
+    [
+     {}
+    ]
+   ],
    "docs/_running-tests/chrome_android.md": [
     [
      {}
     ]
    ],
    "docs/_running-tests/index.md": [
     [
      {}
@@ -547257,22 +547262,26 @@
   "docs/_reviewing-tests/checklist.md": [
    "c3f14eb28a73ec65fe80396c89fe94cd49a698ed",
    "support"
   ],
   "docs/_reviewing-tests/index.md": [
    "e1b4b49cbd7ea1fd703c7ab3814deee0669e9336",
    "support"
   ],
+  "docs/_running-tests/chrome.md": [
+   "a09c8a0ea4d5d2abfd93843176b3c81e22fdbf22",
+   "support"
+  ],
   "docs/_running-tests/chrome_android.md": [
    "082b7697eed61caefcc0a280cba6cee24ff12e7d",
    "support"
   ],
   "docs/_running-tests/index.md": [
-   "ab0156e7fea2e4e462065c458dd8aaf56298150a",
+   "350437f8d19af554887d519013b4bed38fcb1a62",
    "support"
   ],
   "docs/_running-tests/safari.md": [
    "cc0d20587edd9d0e8550b4fa2666d056061d02ee",
    "support"
   ],
   "docs/_writing-tests/ahem.md": [
    "97ee326d501aea007b5f87ee98d0ee6ca303cbb1",
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/tests/docs/_running-tests/chrome.md
@@ -0,0 +1,41 @@
+---
+layout: page
+title: Chrome
+---
+When running Chrome, there are some additional useful command line arguments.
+
+As with most products, you can use a different binary with `--binary`, e.g., to
+run Chrome Dev on Linux:
+
+```
+./wpt run --binary `which google-chrome-unstable` chrome
+```
+
+Extra arguments to Chrome can be passed with `--binary-args`.
+
+To enable all [experimental web platform features](https://www.chromium.org/blink/runtime-enabled-features) (chrome://flags/#enable-experimental-web-platform-features):
+
+```
+./wpt run --binary-arg=--enable-experimental-web-platform-features chrome fullscreen/
+```
+
+To enable a specific [runtime enabled feature](http://dev.chromium.org/blink/runtime-enabled-features):
+
+```
+./wpt run --binary-arg=--enable-blink-features=AsyncClipboard chrome clipboard-apis/
+```
+
+To bypass device selection and use mock media for tests using `getUserMedia`:
+
+```
+./wpt run --binary-arg=--use-fake-ui-for-media-stream --binary-arg=--use-fake-device-for-media-stream chrome mediacapture-streams/
+```
+
+Note: there's an [open issue for doing this using WebDriver](https://github.com/w3c/web-platform-tests/issues/7424).
+
+Some of the above are most useful in combination, e.g., to run all tests in
+Chrome Dev with experimental web platform features enabled:
+
+```
+./wpt run --binary `which google-chrome-unstable` --binary-arg=--enable-experimental-web-platform-features chrome
+```
--- a/testing/web-platform/tests/docs/_running-tests/index.md
+++ b/testing/web-platform/tests/docs/_running-tests/index.md
@@ -22,16 +22,18 @@ Or to run in a specified copy of Firefox
 
 `./wpt run --help` lists the supported products.
 
 For details on the supported products and a large number of other options for
 customising the test run, see `./wpt run --help`.
 
 Additional browser-specific documentation:
 
+  * [Chrome][chrome]
+
   * [Chrome for Android][chrome android]
 
   * [Safari][safari]
 
 ## From Inside a Browser
 Tests that have been merged on GitHub are mirrored at [http://w3c-test.org/][w3c-test].
 
 For running multiple tests inside a browser, there is a test runner
@@ -64,14 +66,15 @@ their type in the repository.
 
 For test execution, please read the documentation for the various test types
 very carefully and then check your understanding on
 the [mailing list][public-test-infra] or [IRC][] ([webclient][web irc], join
 channel `#testing`). It's possible edge-case behavior isn't properly
 documented!
 
 
+[chrome]: {{ site.baseurl }}{% link _running-tests/chrome.md %}
 [chrome android]: {{ site.baseurl }}{% link _running-tests/chrome_android.md %}
 [safari]: {{ site.baseurl }}{% link _running-tests/safari.md %}
 [public-test-infra]: https://lists.w3.org/Archives/Public/public-test-infra/
 [IRC]: irc://irc.w3.org:6667/testing
 [web irc]: http://irc.w3.org
 [w3c-test]: http://w3c-test.org