Mirrors/servo
1
0
Fork 0
mirror of https://github.com/servo/servo.git synced 2025-08-11 16:35:33 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update web-platform-tests to revision 4a5223502fa660ce03e470af6a61c8bc26c5a8ee

Browse source
This commit is contained in:
WPT Sync Bot 2018-04-23 21:13:37 -04:00
parent c5f7c9ccf3
commit e891345f26
1328 changed files with 36632 additions and 20588 deletions
Download patch file Download diff file Expand all files Collapse all files

41
tests/wpt/web-platform-tests/docs/_running-tests/chrome.md Normal file
View file

@ -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
```

3
tests/wpt/web-platform-tests/docs/_running-tests/index.md
View file

@ -27,6 +27,8 @@ customising the test run, see `./wpt run --help`.
Additional browser-specific documentation:
* [Chrome][chrome]
* [Chrome for Android][chrome android]
* [Safari][safari]
@ -69,6 +71,7 @@ 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/