Update web-platform-tests URLs after repo move
Part of https://bit.ly/wpt-transition.
Most of the changes were done as such:
```
git grep -l w3c/web-platform-tests | xargs sed -i 's#https://github.com/w3c/web-platform-tests#https://github.com/web-platform-tests/wpt#g'
git grep -lF 'web-platform-tests.org' | xargs sed -i 's#http://web-platform-tests.org#https://web-platform-tests.org#g'
```
The http => https changes included here because one such URL got
involved in the first after manual tweaks.
Change-Id: Ied8334b88e4a0936cd995a002bb2a502c04ecfc7
Reviewed-on: https://chromium-review.googlesource.com/1080510
Reviewed-by: Tim Volodine <[email protected]>
Reviewed-by: Robert Ma <[email protected]>
Reviewed-by: Rick Byers <[email protected]>
Commit-Queue: Philip Jägenstedt <[email protected]>
Cr-Commit-Position: refs/heads/master@{#563242}diff --git a/docs/testing/layout_tests_tips.md b/docs/testing/layout_tests_tips.md
index fcda5dd8..69efd16 100644
--- a/docs/testing/layout_tests_tips.md
+++ b/docs/testing/layout_tests_tips.md
@@ -20,7 +20,7 @@
## General Principles
This section contains guidelines adopted from
-[web-platform-tests documentation](http://web-platform-tests.org/writing-tests/general-guidelines.html)
+[web-platform-tests documentation](https://web-platform-tests.org/writing-tests/general-guidelines.html)
and
[WebKit's Wiki page on Writing good test cases](https://trac.webkit.org/wiki/Writing%20Layout%20Tests%20for%20DumpRenderTree),
with Blink-specific flavoring.
@@ -93,7 +93,7 @@
`testharness.js` makes a test self-describing when used correctly. Other types
of tests, such as reference tests and
[tests with manual fallback](./layout_tests_with_manual_fallback.md),
-[must be carefully designed](http://web-platform-tests.org/writing-tests/manual.html#requirements-for-a-manual-test)
+[must be carefully designed](https://web-platform-tests.org/writing-tests/manual.html#requirements-for-a-manual-test)
to be self-describing.
### Minimal
@@ -107,7 +107,7 @@
Tests should provide as much relevant information as possible when failing.
`testharness.js` tests should prefer
-[rich assert_ functions](https://github.com/w3c/web-platform-tests/blob/master/docs/_writing-tests/testharness-api.md#list-of-assertions)
+[rich assert_ functions](https://web-platform-tests.org/writing-tests/testharness-api.html#list-of-assertions)
to combining `assert_true()` with a boolean operator. Using appropriate
`assert_` functions results in better diagnostic output when the assertion
fails.
diff --git a/docs/testing/layout_tests_with_manual_fallback.md b/docs/testing/layout_tests_with_manual_fallback.md
index 0d8e3a6..74aa2f9 100644
--- a/docs/testing/layout_tests_with_manual_fallback.md
+++ b/docs/testing/layout_tests_with_manual_fallback.md
@@ -11,7 +11,7 @@
A popular pattern used in these tests is to rely on the user to perform some
manual steps in order to run the test case in a normal browser session. These
tests are effectively
-[manual tests](http://web-platform-tests.org/writing-tests/manual.html), with
+[manual tests](https://web-platform-tests.org/writing-tests/manual.html), with
additional JavaScript code that automatically performs the desired manual steps,
when loaded in an environment that exposes the needed testing APIs.
diff --git a/docs/testing/web_platform_tests.md b/docs/testing/web_platform_tests.md
index d50041d..910962b 100644
--- a/docs/testing/web_platform_tests.md
+++ b/docs/testing/web_platform_tests.md
@@ -5,7 +5,7 @@
mission of improving the web. We believe that leveraging and contributing to a
shared test suite is one of the most important tools in achieving
interoperability between browsers. The [web-platform-tests
-repository](https://github.com/w3c/web-platform-tests) is the primary shared
+repository](https://github.com/web-platform-tests/wpt) is the primary shared
test suite where all browser engines are collaborating.
Chromium has a 2-way import/export process with the upstream web-platform-tests
@@ -13,7 +13,7 @@
[LayoutTests/external/wpt](../../third_party/WebKit/LayoutTests/external/wpt)
and any changes to the imported tests are also exported to web-platform-tests.
-See http://web-platform-tests.org/ for general documentation on
+See https://web-platform-tests.org/ for general documentation on
web-platform-tests, including tips for writing and reviewing tests.
[TOC]
@@ -68,7 +68,7 @@
If you upload a CL with any changes in
[third_party/WebKit/LayoutTests/external/wpt](../../third_party/WebKit/LayoutTests/external/wpt),
once you add reviewers the exporter will create a provisional pull request with
-those changes in the [upstream WPT GitHub repository](https://github.com/w3c/web-platform-tests/).
+those changes in the [upstream WPT GitHub repository](https://github.com/web-platform-tests/wpt/).
Once you're ready to land your CL, please check the Travis CI status on the
upstream PR (link at the bottom of the page). If it's green, go ahead and land your CL
@@ -82,9 +82,9 @@
- CLs that change over 1000 files will not be exported.
- All PRs use the
- [`chromium-export`](https://github.com/w3c/web-platform-tests/pulls?utf8=%E2%9C%93&q=is%3Apr%20label%3Achromium-export) label.
+ [`chromium-export`](https://github.com/web-platform-tests/wpt/pulls?utf8=%E2%9C%93&q=is%3Apr%20label%3Achromium-export) label.
- All PRs for CLs that haven't yet been landed in Chromium also use the
- [`do not merge yet`](https://github.com/w3c/web-platform-tests/pulls?q=is%3Apr+is%3Aopen+label%3A%22do+not+merge+yet%22) label.
+ [`do not merge yet`](https://github.com/web-platform-tests/wpt/pulls?q=is%3Apr+is%3Aopen+label%3A%22do+not+merge+yet%22) label.
- The exporter cannot create upstream PRs for in-flight CLs with binary files (e.g. webm files).
An export PR will still be made after the CL lands.
@@ -184,19 +184,19 @@
is and isn't required.
When implementation experience is needed to inform the specification work,
-[tentative tests](http://web-platform-tests.org/writing-tests/file-names.html)
+[tentative tests](https://web-platform-tests.org/writing-tests/file-names.html)
can be appropriate. It should be apparent in context why the test is tentative
and what needs to be resolved to make it non-tentative.
### Tests that require testing APIs
-[testdriver.js](http://web-platform-tests.org/writing-tests/testdriver.html)
+[testdriver.js](https://web-platform-tests.org/writing-tests/testdriver.html)
provides a means to automate tests that cannot be written purely using web
platform APIs, similar to `internals.*` and `eventSender.*` in regular Blink
layout tests.
If no testdriver.js API exists, check if it's a
-[known issue](https://github.com/w3c/web-platform-tests/labels/testdriver.js)
+[known issue](https://github.com/web-platform-tests/wpt/labels/testdriver.js)
and otherwise consider filing a new issue.
An alternative is to write manual tests that are automated with scripts from
@@ -240,7 +240,7 @@
### Direct pull requests
It's still possible to make direct pull requests to web-platform-tests, see
-http://web-platform-tests.org/appendix/github-intro.html.
+https://web-platform-tests.org/appendix/github-intro.html.
## Running tests
diff --git a/docs/testing/writing_layout_tests.md b/docs/testing/writing_layout_tests.md
index 7d90642..f71eb3a 100644
--- a/docs/testing/writing_layout_tests.md
+++ b/docs/testing/writing_layout_tests.md
@@ -73,7 +73,7 @@
Tests should be written under the assumption that they will be upstreamed
to the WPT project. To this end, tests should follow the
-[WPT guidelines](http://web-platform-tests.org/writing-tests/).
+[WPT guidelines](https://web-platform-tests.org/writing-tests/).
There is no style guide that applies to all layout tests. However, some projects
@@ -93,18 +93,18 @@
less reliable tests.
All new JavaScript tests should be written using the
-[testharness.js](https://github.com/w3c/web-platform-tests/tree/master/resources)
+[testharness.js](https://github.com/web-platform-tests/wpt/tree/master/resources)
testing framework. This framework is used by the tests in the
-[web-platform-tests](https://github.com/w3c/web-platform-tests) repository,
+[web-platform-tests](https://github.com/web-platform-tests/wpt) repository,
which is shared with all the other browser vendors, so `testharness.js` tests
are more accessible to browser developers.
-See the [API documentation](http://web-platform-tests.org/writing-tests/testharness-api.html)
+See the [API documentation](https://web-platform-tests.org/writing-tests/testharness-api.html)
for a thorough introduction to `testharness.js`.
Layout tests should follow the recommendations of the above documentation.
Furthermore, layout tests should include relevant
-[metadata](http://web-platform-tests.org/writing-tests/css-metadata.html). The
+[metadata](https://web-platform-tests.org/writing-tests/css-metadata.html). The
specification URL (in `<link rel="help">`) is almost always relevant, and is
incredibly helpful to a developer who needs to understand the test quickly.
@@ -190,7 +190,7 @@
This is contrary to the WPT guidelines, which call for absolute paths.
This limitation does not apply to the tests in `LayoutTests/http`, which rely on
an HTTP server, or to the tests in `LayoutTests/external/wpt`, which are
-imported from the [WPT repository](https://github.com/w3c/web-platform-tests).
+imported from the [WPT repository](https://github.com/web-platform-tests/wpt).
***
### WPT Supplemental Testing APIs
@@ -362,7 +362,7 @@
cannot be covered by JavaScript tests.
New reference tests should follow the
-[WPT reftests guidelines](http://web-platform-tests.org/writing-tests/reftests.html).
+[WPT reftests guidelines](https://web-platform-tests.org/writing-tests/reftests.html).
The most important points are summarized below.
* 🚧 The test page declares the reference page using a
@@ -435,7 +435,7 @@
Pixel tests should still follow the principles laid out above. Pixel tests pose
unique challenges to the desire to have *self-describing* and *cross-platform*
tests. The
-[WPT rendering test guidelines](http://web-platform-tests.org/writing-tests/rendering.html)
+[WPT rendering test guidelines](https://web-platform-tests.org/writing-tests/rendering.html)
contain useful guidance. The most relevant pieces of advice are below.
* Whenever possible, use a green paragraph / page / square to indicate success.
