Update web-platform-tests to revision 0d4300c5045a5587c2eb3d1416b11ffeecf5dadc

tests/wpt/web-platform-tests/docs/Makefile

@@ -13,11 +13,12 @@ help:
 
 .PHONY: help Makefile
 
-tools/wptserve:
+tools/%:
 	mkdir -p $(shell dirname $@)
-	ln -s ../../tools/wptserve $@
+	test -d ../$@
+	ln -s ../../$@ $@
 
 # Catch-all target: route all unknown targets to Sphinx using the new
 # "make mode" option.  $(O) is meant as a shortcut for $(SPHINXOPTS).
-%: Makefile tools/wptserve
+%: Makefile tools/wptserve tools/certs
 	@$(SPHINXBUILD) -M $@ "$(SOURCEDIR)" "$(BUILDDIR)" $(SPHINXOPTS) $(O)

tests/wpt/web-platform-tests/docs/appendix/index.md

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

tests/wpt/web-platform-tests/docs/index.md

@@ -53,10 +53,9 @@ free to add yourself to the META.yml file!
    writing-tests/index
    reviewing-tests/index
    admin/index
-   appendix/index
 ```
 
 [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
-[github-intro]: appendix/github-intro
+[github-intro]: writing-tests/github-intro

tests/wpt/web-platform-tests/docs/make.bat

@@ -28,6 +28,7 @@ if errorlevel 9009 (
 if not exist tools\ ( mkdir tools )
 
 if not exist tools\wptserve\ ( mklink /d tools\wptserve ..\..\tools\wptserve )
+if not exist tools\certs\ ( mklink /d tools\certs ..\..\tools\certs )
 
 %SPHINXBUILD% -M %1 %SOURCEDIR% %BUILDDIR% %SPHINXOPTS%
 goto end

tests/wpt/web-platform-tests/docs/reviewing-tests/git.md

@@ -76,8 +76,8 @@ 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>`
 
-[clone]: ../appendix/github-intro.html#clone
-[commit]: ../appendix/github-intro.html#commit
-[configure]: ../appendix/github-intro.html#configure-remote-upstream
-[fork]: ../appendix/github-intro.html#fork-the-test-repository
-[submit]: ../appendix/github-intro.html#submit
+[clone]: ../writing-tests/github-intro.html#clone
+[commit]: ../writing-tests/github-intro.html#commit
+[configure]: ../writing-tests/github-intro.html#configure-remote-upstream
+[fork]: ../writing-tests/github-intro.html#fork-the-test-repository
+[submit]: ../writing-tests/github-intro.html#submit

tests/wpt/web-platform-tests/docs/reviewing-tests/index.md

@@ -10,6 +10,7 @@ suites, test contributions must be reviewed by a peer.
    checklist
    email
    git
+   reverting
 ```
 
 ## Test Review Policy

tests/wpt/web-platform-tests/docs/running-tests/from-local-system.md

@@ -104,7 +104,7 @@ https://web-platform.test:8443/tools/runner/index.html *
 This server has all the capabilities of the publicly-deployed version--see
 [Running the Tests from the Web](from-web).
 
-\**See [Trusting Root CA](https://github.com/web-platform-tests/wpt/blob/master/README.md#trusting-root-ca)*
+\**See [Trusting Root CA](../tools/certs/README.md)*
 
 ## Via the command line
 

tests/wpt/web-platform-tests/docs/running-tests/index.md

@@ -6,6 +6,7 @@
    from-web
    from-local-system
    custom-runner
+   ../tools/certs/README.md
 ```
 
 The simplest way to run the tests is via the public website. More detail on

tests/wpt/web-platform-tests/docs/writing-tests/index.md

@@ -26,8 +26,11 @@ There's also a load of [general guidelines](general-guidelines) that apply to al
    testdriver
    testdriver-tutorial
    testharness
+   tools
    visual
    wdspec
+   test-templates
+   github-intro
 ```
 
 ## Test Type

tests/wpt/web-platform-tests/docs/writing-tests/reftest-tutorial.md

@@ -19,7 +19,7 @@ You'll need to [configure your system to use WPT's
 tools](../running-tests/from-local-system), but you won't need them until
 towards the end of this tutorial. Although it includes some very brief
 instructions on using git, you can find more guidance in [the tutorial for git
-and GitHub](../appendix/github-intro).
+and GitHub](../writing-tests/github-intro).
 
 WPT's reftests are great for testing web-platform features that have some
 visual effect. [The reftests reference page](reftests) describes them in the
@@ -264,7 +264,7 @@ And now we can push the commit to our fork of WPT:
 The last step is to submit the test for review. WPT doesn't actually need the
 test we wrote in this tutorial, but if we wanted to submit it for inclusion in
 the repository, we would create a pull request on GitHub. [The guide on git and
-GitHub](../appendix/github-intro) has all the details on how to do that.
+GitHub](../writing-tests/github-intro) has all the details on how to do that.
 
 ## More practice
 

tests/wpt/web-platform-tests/docs/writing-tests/submission-process.md

@@ -31,7 +31,7 @@ on, e.g. `git checkout -b topic-name`
   request will be automatically merged.
 
 For detailed guidelines on setup and each of these steps, please refer to the
-[Github Test Submission](../appendix/github-intro) documentation.
+[Github Test Submission](../writing-tests/github-intro) documentation.
 
 Hop on to the [mailing list][public-test-infra] or [IRC][]
 ([webclient][web irc], join channel `#testing`) if you have an issue.  There is

tests/wpt/web-platform-tests/docs/writing-tests/tools.md

@@ -0,0 +1,25 @@
+# Command-line utility scripts
+
+Sometimes you may want to add a script to the repository that's meant to be
+used from the command line, not from a browser (e.g., a script for generating
+test files). If you want to ensure (e.g., for security reasons) that such
+scripts won't be handled by the HTTP server, but will instead only be usable
+from the command line, then place them in either:
+
+* the `tools` subdir at the root of the repository, or
+
+* the `tools` subdir at the root of any top-level directory in the repository
+  which contains the tests the script is meant to be used with
+
+Any files in those `tools` directories won't be handled by the HTTP server;
+instead the server will return a 404 if a user navigates to the URL for a file
+within them.
+
+If you want to add a script for use with a particular set of tests but there
+isn't yet any `tools` subdir at the root of a top-level directory in the
+repository containing those tests, you can create a `tools` subdir at the root
+of that top-level directory and place your scripts there.
+
+For example, if you wanted to add a script for use with tests in the
+`notifications` directory, create the `notifications/tools` subdir and put your
+script there.