Mirrors/servo
1
0
Fork 0
mirror of https://github.com/servo/servo.git synced 2025-08-03 12:40:06 +01:00
Code Issues Projects Releases Packages Wiki Activity

Update web-platform-tests to revision d7afcb8708eac08a614d161d5622a48172daf7e3

Browse source
This commit is contained in:
WPT Sync Bot 2019-05-15 10:40:54 -04:00 • committed by Josh Matthews
parent 6f8bb4dd40
commit edff458e23
791 changed files with 17647 additions and 10322 deletions
Download patch file Download diff file Expand all files Collapse all files

400
tests/wpt/web-platform-tests/docs/appendix/github-intro.md Normal file
View file

@ -0,0 +1,400 @@
# Introduction to GitHub
All the basics that you need to know are documented on this page, but for the
full GitHub documentation, visit [help.github.com][help].
If you are already an experienced Git/GitHub user, all you need to know is that
we use the [normal GitHub Pull Request workflow][github flow] for test
submissions.
If you are a first-time GitHub user, read on for more details of the workflow.
## Setup
1. Create a GitHub account if you do not already have one on
[github.com][github].
2. Download and install the latest version of Git:
[https://git-scm.com/downloads][git]; please refer to the instructions there
for different platforms.
3. Configure your settings so your commits are properly labeled:
On Mac or Linux or Solaris, open the Terminal.
On Windows, open Git Bash (From the Start Menu > Git > Git Bash).
At the prompt, type:
$ git config --global user.name "Your Name"
_This will be the name that is displayed with your test submissions_
Next, type:
$ git config --global user.email "your_email@address.com"
_This should be the email address you used to create the account in Step 1._
4. (Optional) If you don't want to enter your username and password every
time you talk to the remote server, you'll need to set up password caching.
See [Caching your GitHub password in Git][password-caching].
## Fork the test repository
Now that you have Git set up, you will need to fork the test repository. This
will enable you to [submit](#submit) your tests using a pull request (more on this
[below](#submit)).
1. In the browser, go to [web-platform-tests on GitHub][main-repo].
2. Click the ![fork](/assets/forkbtn.png) button in the upper right.
3. The fork will take several seconds, then you will be redirected to your
GitHub page for this forked repository.
You will now be at
**https://github.com/username/wpt**.
4. After the fork is complete, you're ready to [clone](#clone).
## Clone
If your [fork](#fork) was successful, the next step is to clone (download a copy of the files).
### Clone the test repo
At the command prompt, cd into the directory where you want to keep the tests.
$ git clone https://github.com/username/wpt.git
_This will download the tests into a directory named for the repo:_ `wpt/`.
* You should now have a full copy of the test repository on your local
machine. Feel free to browse the directories on your hard drive. You can also
browse them on [github.com][github-w3c] and see the full history of contributions
there.
## Configure Remote / Upstream
Synchronizing your forked repository with the W3C repository will enable you to
keep your forked local copy up-to-date with the latest commits in the W3C
repository.
1. On the command line, navigate to to the directory where your forked copy of
the repository is located.
2. Make sure that you are on the master branch. This will be the case if you
just forked, otherwise switch to master.
$ git checkout master
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/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:
$ git fetch upstream
Then merge them into your local repository:
$ git merge upstream/master
For additional information, please see the [GitHub docs][github-fork-docs].
## Configure your environment
If all you intend to do is to load [manual tests](../writing-tests/manual) or [ref tests](../writing-tests/reftests) from your local file system,
the above setup should be sufficient.
But many tests (and in particular, all [testharness.js tests](../writing-tests/testharness)) require a local web server.
See [Local Setup][local-setup] for more information.
## Branch
Now that you have everything locally, create a branch for your tests.
_Note: If you have already been through these steps and created a branch
and now want to create another branch, you should always do so from the
master branch. To do this follow the steps from the beginning of the [previous
section](#configure-remote-upstream). If you don't start with a clean master
branch you will end up with a big nested mess._
At the command line:
$ git checkout -b topic
This will create a branch named `topic` and immediately
switch this to be your active working branch.
_The branch name should describe specifically what you are testing.
For Example:_
$ git checkout -b flexbox-flex-direction-prop
You're ready to start writing tests! Come back to this page you're ready to
[commit](#commit) them or [submit](#submit) them for review.
## Commit
Before you submit your tests for review and contribution to the main test
repo, you'll need to first commit them locally, where you now have your own
personal version control system with git. In fact, as you are writing your
tests, you may want to save versions of your work as you go before you submit
them to be reviewed and merged.
1. When you're ready to save a version of your work, go to the command
prompt and cd to the directory where your files are.
2. First, ask git what new or modified files you have:
$ git status
_This will show you files that have been added or modified_.
3. For all new or modified files, you need to tell git to add them to the
list of things you'd like to commit:
$ git add [file1] [file2] ... [fileN]
Or:
$ git add [directory_of_files]
4. Run `git status` again to see what you have on the 'Changes to be
committed' list. These files are now 'staged'.
5. Alternatively, you can run `git diff --staged`, which will show you the
diff of things to be committed.
6. Once you've added everything, you can commit and add a message to this
set of changes:
$ git commit -m "Tests for indexed getters in the HTMLExampleInterface"
7. Repeat these steps as many times as you'd like before you submit.
## Verify
The Web Platform Test project has an automated tool
to verify that coding conventions have been followed,
and to catch a number of common mistakes.
You can and should run this tool locally.
It will be run on your submissions anyway,
and any failure will be grounds for rejection,
so you might as well fix them first.
1. On the command line, navigate to to the directory where your clone
of the repository is located.
2. Run `./wpt lint`
3. Fix any mistake it reports and [commit](#commit) again.
For more details, see the [documentation about the lint tool](../writing-tests/lint-tool).
## Submit
If you're here now looking for more instructions, that means you've written
some awesome tests and are ready to submit them. Congratulations and welcome
back!
1. The first thing you do before submitting them to the W3C repo is to push
them back up to the server:
$ git push origin topic
_Note: Here,_ `origin` _refers to remote repo from which you cloned
(downloaded) the files after you forked, referred to as
web-platform-tests.git in the previous example;_
`topic` _refers to the name of your local branch that
you want to push_.
2. Now you can send a message that you have changes or additions you'd like
to be reviewed and merged into the main (original) test repository. You do
this by using a pull request. In a browser, open the GitHub page for your
forked repository: **https://github.com/username/wpt**.
3. Now create the pull request. There are several ways to create a PR in the
GitHub UI. Below is one method and others can be found on
[GitHub.com][github-createpr]
1. Click the ![new pull request](../assets/pullrequestbtn.png) button.
2. On the left, you should see the base repo is the
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'_,
make sure your fork and your `topic`
branch is selected on the right side.
3. Select the ![create pull request](../assets/createpr.png) button at the top.
4. Scroll down and review the diff
5. Scroll back up and in the Title field, enter a brief description for
your submission.
Example: "Tests for CSS Transforms skew() function."
6. If you'd like to add more detailed comments, use the comment field
below.
7. Click ![the create pull request button](../assets/createpr.png)
4. Wait for feedback on your pull request and once your pull request is
accepted, delete your branch (see '[When Pull Request is Accepted](#cleanup)').
That's it! Your pull request will go into a queue and will be reviewed soon.
## Modify
Once you submit your pull request, a reviewer will check your proposed changes
for correctness and style. It is likely that this process will lead to some
comments asking for modifications to your code. When you are ready to make the
changes, follow these steps:
1. Check out the branch corresponding to your changes e.g. if your branch was
called `topic`
run:
$ git checkout topic
2. Make the changes needed to address the comments, and commit them just like
before.
3. Push the changes to the remote branch containing the pull request:
$ git push origin topic
4. The pull request will automatically be updated with the new commit.
Sometimes it takes multiple iterations through a review before the changes are
finally accepted. Don't worry about this; it's totally normal. The goal of test
review is to work together to create the best possible set of tests for the web
platform.
## Cleanup
Once your pull request has been accepted, you will be notified in the GitHub
UI and you may get an email. At this point, your changes have been merged
into the main test repository. You do not need to take any further action
on the test but you should delete your branch. This can easily be done in
the GitHub UI by navigating to the pull requests and clicking the
'Delete Branch' button.
![pull request accepted delete branch](/assets/praccepteddelete.png)
Alternatively, you can delete the branch on the command line.
$ git push origin --delete <branchName>
## Tips & Tricks
The following workflow is recommended:
1. Start branch based on latest w3c/master
2. Write tests
3. Rebase onto latest w3c/master
4. Submit tests
5. Stop fiddling with the branch base until review is done
6. After the PR has been accepted, delete the branch. (Every new PR should
come from a new branch.)
7. Synchronize your fork with the W3C repository by fetching your upstream and
merging it. (See '[Configure Remote / Upstream](#configure-remote-upstream)')
You need to be able to set up remote upstream, etc. Please refer to [Pro Git
Book][git-book] and enjoy reading.
## Working with Pull Requests as a reviewer
In order to do a thorough review,
it is sometimes desirable to have a local copy of the tests one wishes to review.
Reviewing tests also often results in wanting a few things to be changed.
Generally, the reviewer should ask the author to make the desired changes.
However, sometimes the original author does not respond to the requests,
or the changes are so trivial (e.g. fixing a typo)
that bothering the original author seems like a waste of time.
Here is how to do all that.
### Trivial cases
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/web-platform-tests/wpt/pull/1234
2. Go to the ![Files changed](../assets/files-changed.png) 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](../assets/pencil-icon.png) icon in the upper right corner
4. Make the desired change
5. Write a commit message (including a good title) at the bottom
6. Make sure the ![Commit directly to the [name-of-the-PR-branch] branch.](../assets/commit-directly.png) radio button is selected.
_Note: If the PR predates the introduction of this feature by Github,
or if the author of the PR has disabled write-access by reviewers to the PR branch,
this may not be available,
and your only option would be to commit to a new branch, creating a new PR._
7. Click the ![Commit Changes](../assets/commitbtn.png) button.
### The Normal Way
This is how to import the Pull Request's branch
into your existing local checkout of the repository.
If you don't have one, go [fork](#fork), [clone](#clone), and [configure](#configure-remote--upstream) it.
1. Move into your local clone: `cd wherever-you-put-your-repo`
2. Add a remote for the PR author's repo: `git remote add <author-id> git://github.com/<author-id>/<repo-name>.git`
3. Fetch the PR: `git fetch <author-id> <name-of-the-PR-branch>`
4. Checkout that branch: `git checkout <name-of-the-PR-branch>`
_The relevant `<author-id>`, `<repo-name>`, and `<name-of-the-PR-branch>` can be found by looking for this sentence in on the Github page of the PR:
![Add more commits by pushing to the name-of-the-PR-branch branch on author-id/repo-name.](../assets/more-commits.png)_
If all you meant to do was reviewing files locally, you're all set.
If you wish to make changes to the PR branch:
1. Make changes and [commit](#commit) normally
2. Push your changes upstream: `git push <author-id> <name-of-the-PR-branch>`
_Note: If the PR predates the introduction of this feature by Github,
or if the author of the PR has disabled write-access by reviewers to the PR branch,
this will not work, and you will need to use the alternative described below._
If, instead of modifying the existing PR, you wish to make a new one based on it:
1. Set up a new branch that contains the existing PR by doing one of the following:
1. Create a new branch from the tip of the PR:
`git branch <your-new-branch> <name-of-the-PR-branch> && git checkout <your-new-branch>`
2. Create a new branch from `master` and merge the PR into it:
`git branch <your-new-branch> master && git checkout <your-new-branch> && git merge <name-of-the-PR-branch>`
2. Make changes and [commit](#commit) normally
3. Push your changes to **your** repo: `git push origin <your-new-branch>`
4. Go to the Github Web UI to [submit a new Pull Request](#submit).
_Note: You should also close the original pull request._
When you're done reviewing or making changes,
you can delete the branch: `git branch -d <name-of-the-PR-branch>`
(use `-D` instead of `-d` to delete a branch that has not been merged into master yet).
If you do not expect work with more PRs from the same author,
you may also discard your connection to their repo:
`git remote remove <author-id>`
[local-setup]: ../introduction#local-setup
[git]: https://git-scm.com/downloads
[git-book]: https://git-scm.com/book
[github]: https://github.com/
[github-w3c]: https://github.com/w3c
[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/web-platform-tests/wpt
[password-caching]: https://help.github.com/articles/caching-your-github-password-in-git
[github flow]: https://guides.github.com/introduction/flow/

10
tests/wpt/web-platform-tests/docs/appendix/index.md Normal file
View file

@ -0,0 +1,10 @@
# Appendices
```eval_rst
.. toctree ::
:maxdepth: 1
github-intro
reverting
test-templates
```

28
tests/wpt/web-platform-tests/docs/appendix/reverting.md Normal file
View file

@ -0,0 +1,28 @@
# Reverting Changes
Testing is imperfect and from time to time changes are merged into master which
break things for users of web-platform-tests. Such breakage can include:
* Failures in Travis or Taskcluster runs for this repository, either on the
master branch or on pull requests following the breaking change.
* Breakage in browser engine repositories which import and run
web-platform-tests, such as Chromium, Edge, Gecko, Servo and WebKit.
* Breakage in results collections systems for results dashboards, such as
[wpt.fyi](https://wpt.fyi).
* Breakage in supplemental tooling used by working groups, such as the
[CSS build system][].
When such breakage happens, if the maintainers of the affected systems request
it, pull requests to revert the original change should normally be approved and
merged as soon as possible. (When the original change itself was fixing a
serious problem, it's a judgement call, but prefer the fastest path to a stable
state acceptable to everyone.)
Once a revert has happened, the maintainers of the affected systems are
expected to work with the original patch author to resolve the problem so that
the change can be relanded. A reasonable timeframe to do so is within one week.
[CSS build system]: https://github.com/web-platform-tests/wpt/tree/master/css/tools

74
tests/wpt/web-platform-tests/docs/appendix/test-templates.md Normal file
View file

@ -0,0 +1,74 @@
# Test Templates
This page contains templates for creating tests. The template syntax
is compatible with several popular editors including TextMate, Sublime
Text, and emacs' YASnippet mode.
Templates for filenames are also given. In this case `{}` is used to
delimit text to be replaced and `#` represents a digit.
## Reftests
### Test
``` html
<!DOCTYPE html>
<meta charset="utf-8">
<title>${1:Test title}</title>
<link rel="match" href="${2:URL of match}">
<style>
${3:Test CSS}
</style>
<body>
${4:Test content}
</body>
```
Filename: `{test-topic}-###.html`
### Reference:
``` html
<!DOCTYPE html>
<meta charset="utf-8">
<title>${1:Reference title}</title>
<style>
${2:Reference CSS}
</style>
<body>
${3:Reference content}
</body>
```
Filename: `{description}.html` or `{test-topic}-###-ref.html`
## testharness.js tests
``` html
<!DOCTYPE html>
<meta charset="utf-8">
<title>${1:Test title}</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script>
${2:Test body}
</script>
```
Filename: `{test-topic}-###.html`
### Manual Test
``` html
<!DOCTYPE html>
<meta charset="utf-8">
<title>${1:Test title}</title>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script>
setup({explicit_timeout: true});
${2:Test body}
</script>
```
Filename: `{test-topic}-###-manual.html`