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

Update web-platform-tests to revision cf261625e2d230ab219eec966f4abe26e3401b64

Browse source
This commit is contained in:
WPT Sync Bot 2018-05-29 21:17:45 -04:00
parent 11a89bcc47
commit 8f98acd0e7
297 changed files with 3396 additions and 1555 deletions
Download patch file Download diff file Expand all files Collapse all files

12
tests/wpt/web-platform-tests/docs/_appendix/github-intro.md
View file

@ -48,7 +48,7 @@ If you are a first-time GitHub user, read on for more details of the workflow.
The test repository that you contribute to will depend on the specification
that you are testing.
**Main W3C test repository**: [github.com/w3c/web-platform-tests][main-repo]
**Main W3C test repository**: [github.com/web-platform-tests/wpt][main-repo]
## Fork
@ -111,7 +111,7 @@ repository.
3. Next, add the remote of the repository your forked. This assigns the
original repository to a remote called "upstream":
$ git remote add upstream https://github.com/w3c/web-platform-tests.git
$ git remote add upstream https://github.com/web-platform-tests/wpt.git
4. To pull in changes in the original repository that are not present in your
local repository first fetch them:
@ -219,7 +219,7 @@ GitHub UI. Below is one method and others can be found on
of the UI, then click the ![new pull request][pullrequestbtn] button.
2. On the left, you should see the base repo is the
w3c/web-platform-tests. On the right, you should see your fork of that
web-platform-tests/wpt. On the right, you should see your fork of that
repo. In the branch menu of your forked repo, switch to `topic`
**Note:** If you see _'There isn't anything to compare'_, click
@ -323,8 +323,8 @@ If it is possible to review the tests without a local copy,
but the reviewer still wants to make some simple tweaks to the tests before merging,
it is possible to do so via the Github web UI.
1. Open the pull request. E.g. https://github.com/w3c/web-platform-tests/pull/1234
2. Go to the ![Files changed][files-changed] view (e.g. https://github.com/w3c/web-platform-tests/pull/1234/files)
1. Open the pull request. E.g. https://github.com/web-platform-tests/wpt/pull/1234
2. Go to the ![Files changed][files-changed] view (e.g. https://github.com/web-platform-tests/wpt/pull/1234/files)
3. Locate the files you wish to change, and click the ![pencil][pencil-icon] icon in the upper right corner
4. Make the desired change
5. Write a commit message (including a good title) at the bottom
@ -393,7 +393,7 @@ you may also discard your connection to their repo:
[github-fork-docs]: https://help.github.com/articles/fork-a-repo
[github-createpr]: https://help.github.com/articles/creating-a-pull-request
[help]: https://help.github.com/
[main-repo]: https://github.com/w3c/web-platform-tests
[main-repo]: https://github.com/web-platform-tests/wpt
[password-caching]: https://help.github.com/articles/caching-your-github-password-in-git
[pullrequestlink]: {{ site.baseurl }}{% link /assets/pullrequestlink.png %}
[pullrequestbtn]: {{ site.baseurl }}{% link /assets/pullrequestbtn.png %}

2
tests/wpt/web-platform-tests/docs/_includes/header.html
View file

@ -1,6 +1,6 @@
<header class="site-header" role="banner">
<a class="github-fork-ribbon left-top" href="https://github.com/w3c/web-platform-tests/blob/master/docs/{{ page.path }}" data-ribbon="Edit on GitHub">Edit on GitHub</a>
<a class="github-fork-ribbon left-top" href="https://github.com/web-platform-tests/wpt/blob/master/docs/{{ page.path }}" data-ribbon="Edit on GitHub">Edit on GitHub</a>
<div class="wrapper">

2
tests/wpt/web-platform-tests/docs/_reviewing-tests/checklist.md
View file

@ -7,7 +7,7 @@ order: 2
The following checklist is provided as a guideline to assist in reviewing
tests; in case of any contradiction with requirements stated elsewhere in the
documentation it should be ignored
(please [file a bug](https://github.com/w3c/web-platform-tests/issues/new)!).
(please [file a bug](https://github.com/web-platform-tests/wpt/issues/new)!).
As noted on the [reviewing tests][review index] page, nits need not block PRs
from landing.

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

@ -31,7 +31,7 @@ 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).
Note: there's an [open issue for doing this using WebDriver](https://github.com/web-platform-tests/wpt/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:

2
tests/wpt/web-platform-tests/docs/_running-tests/chrome_android.md
View file

@ -24,7 +24,7 @@ Until we find a better way, we need to root the Android device and update the
## CA certificate
In order to run HTTPS tests, we need to add
[WPT's CA](https://github.com/w3c/web-platform-tests/blob/master/tools/certs/cacert.pem)
[WPT's CA](https://github.com/web-platform-tests/wpt/blob/master/tools/certs/cacert.pem)
to the phone. First, convert the certificate from PEM to CRT:
```

2
tests/wpt/web-platform-tests/docs/_running-tests/safari.md
View file

@ -14,7 +14,7 @@ To run Safari on macOS, some manual setup is required:
* Set `OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES` in your environment. This is a
workaround for a known
[macOS High Sierra issue](https://github.com/w3c/web-platform-tests/issues/9007).
[macOS High Sierra issue](https://github.com/web-platform-tests/wpt/issues/9007).
Now, run the tests using the `safari` product:
```

2
tests/wpt/web-platform-tests/docs/_writing-tests/ahem.md
View file

@ -86,4 +86,4 @@ On Linux, copy the file to `~/.local/share/fonts` and then run
`fc-cache`.
[ahem-readme]: https://www.w3.org/Style/CSS/Test/Fonts/Ahem/README
[download-ahem]: https://github.com/w3c/web-platform-tests/raw/master/fonts/Ahem.ttf
[download-ahem]: https://github.com/web-platform-tests/wpt/raw/master/fonts/Ahem.ttf

2
tests/wpt/web-platform-tests/docs/_writing-tests/submission-process.md
View file

@ -41,7 +41,7 @@ Hop on to the [mailing list][public-test-infra] or [IRC][]
no need to announce your review request, as soon as you make a Pull Request
GitHub will inform interested parties.
[repo]: https://github.com/w3c/web-platform-tests/
[repo]: https://github.com/web-platform-tests/wpt/
[github-intro]: {{ site.baseurl }}{% link _appendix/github-intro.md %}
[github flow]: https://guides.github.com/introduction/flow/
[public-test-infra]: https://lists.w3.org/Archives/Public/public-test-infra/

2
tests/wpt/web-platform-tests/docs/_writing-tests/testdriver-tutorial.md
View file

@ -313,5 +313,5 @@ run instead of testdriver-extra.js in browser specific test environments. For ex
### What if I need to return a value from my testdriver API?
We currently don't have this capability, but it is coming soon and will be documented. The bug is [here](https://github.com/w3c/web-platform-tests/issues/10716)
We currently don't have this capability, but it is coming soon and will be documented. The bug is [here](https://github.com/web-platform-tests/wpt/issues/10716)

4
tests/wpt/web-platform-tests/docs/introduction.md
View file

@ -76,7 +76,7 @@ The testsuite has a few types of tests, outlined below:
## GitHub
[GitHub](https://github.com/w3c/web-platform-tests/) is used both for [issue tracking](https://github.com/w3c/web-platform-tests/issues) and [test submissions](https://github.com/w3c/web-platform-tests/pulls); we
[GitHub](https://github.com/web-platform-tests/wpt/) is used both for [issue tracking](https://github.com/web-platform-tests/wpt/issues) and [test submissions](https://github.com/web-platform-tests/wpt/pulls); we
provide [a limited introduction][github-intro] to both git and
GitHub.
@ -148,7 +148,7 @@ After your `hosts` file is configured, the servers will be locally accessible at
http://web-platform.test:8000/<br>
https://web-platform.test:8443/ *
\**See [Trusting Root CA](https://github.com/w3c/web-platform-tests/blob/master/README.md#trusting-root-ca)*
\**See [Trusting Root CA](https://github.com/web-platform-tests/wpt/blob/master/README.md#trusting-root-ca)*
## Running tests automatically