Merge pull request #1889 from foolip/update-wpt-url

Update web-platform-tests URLs

CONTRIBUTING.md

@@ -50,4 +50,4 @@ Example (defining): `<dfn>[[\FooBar]]</dfn>`\
 Example (referencing): `<a>[[\FooBar]]</a>`
 
 ### Tests
-For normative changes, a corresponding [web-platform-tests](https://github.com/w3c/web-platform-tests) PR is highly appreciated. Typically, both PRs will be merged at the same time. Note that a test change that contradicts the spec should not be merged before the corresponding spec change. If testing is not practical, please explain why and if appropriate [file a web-platform-tests issue](https://github.com/w3c/web-platform-tests/issues/new) to follow up later. Add the `type:untestable` or `type:missing-coverage` label as appropriate.
+For normative changes, a corresponding [web-platform-tests](https://github.com/web-platform-tests/wpt) PR is highly appreciated. Typically, both PRs will be merged at the same time. Note that a test change that contradicts the spec should not be merged before the corresponding spec change. If testing is not practical, please explain why and if appropriate [file a web-platform-tests issue](https://github.com/web-platform-tests/wpt/issues/new) to follow up later. Add the `type:untestable` or `type:missing-coverage` label as appropriate.

TESTING.md

@@ -14,7 +14,7 @@ https://wpt.fyi/webrtc/RTCDataChannelEvent-constructor.html
 
 ## Naming Guidelines
 
-Update to WebIDL definitions in the spec must also update the IDL test file at [/interfaces/webrtc-pc.idl](https://github.com/w3c/web-platform-tests/blob/master/interfaces/webrtc-pc.idl).
+Update to WebIDL definitions in the spec must also update the IDL test file at [/interfaces/webrtc-pc.idl](https://github.com/web-platform-tests/wpt/blob/master/interfaces/webrtc-pc.idl).
 A [helper script](http://web-platform-tests.org/writing-tests/idlharness.html)
 can be pasted in the console to generate IDL code from the spec HTML. Note that
 partial dictionary definition is not supported in idlharness.js, so some manual

webrtc.html

@@ -26,7 +26,7 @@
 
     <p>While the specification is feature complete and is expected to be stable, there are also a number of <a href="https://github.com/w3c/webrtc-pc/issues?utf8=%E2%9C%93&amp;q=is%3Aopen%20is%3Aissue%20-label%3AEditorial%20">known substantive issues</a> on the specification that will be addressed during the Candidate Recommendation period based on implementation experience feedback.</p>
 
-    <p>It might also evolve based on feedback gathered as its <a href="https://github.com/w3c/web-platform-tests/tree/master/webrtc">associated test suite</a> evolves. This test suite will be used to build an <a href="https://wpt.fyi/webrtc">implementation report</a> of the API.</p>
+    <p>It might also evolve based on feedback gathered as its <a href="https://github.com/web-platform-tests/wpt/tree/master/webrtc">associated test suite</a> evolves. This test suite will be used to build an <a href="https://wpt.fyi/webrtc">implementation report</a> of the API.</p>
 
     <p>To go into Proposed Recommendation status, the group expects to demonstrate implementation of each feature in at least two deployed browsers, and at least one implementation of each optional feature. Mandatory feature with only one implementation may be marked as optional in a revised Candidate Recommendation where applicable.</p>
 

webrtc.js

@@ -94,7 +94,7 @@ var respecConfig = {
   // Team Contact.
   wgPatentURI:  "https://www.w3.org/2004/01/pp-impl/47318/status",
   issueBase: "https://github.com/w3c/webrtc-pc/issues/",
-  testSuiteURI: "https://github.com/w3c/web-platform-tests/tree/master/webrtc",
+  testSuiteURI: "https://github.com/web-platform-tests/wpt/tree/master/webrtc",
   otherLinks: [
     {
       key: "Participate",