Update links to layout test documentation.

BUG=665494

Review-Url: https://codereview.chromium.org/2505683002
Cr-Commit-Position: refs/heads/master@{#432639}

Author: qyearsley

docs/android_test_instructions.md

@@ -298,8 +298,7 @@ You might want to add stars `*` to each as a regular expression, e.g.
 
 ## Running Blink Layout Tests
 
-See
-https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tests
+See [Layout Tests](testing/layout_tests.md).
 
 ## Running GPU tests
 

docs/how_to_extend_layout_test_framework.md

@@ -12,8 +12,8 @@ to help people who want to actually the framework to test whatever they want.
 ## Background
 
 Before you can start actually extending the framework, you should be familiar
-with how to use it. This wiki is basically all you need to learn how to use it
-http://www.chromium.org/developers/testing/webkit-layout-tests
+with how to use it. See the
+[layout tests documentation](testing/layout_tests.md).
 
 ## How to Extend the Framework
 
@@ -129,7 +129,7 @@ Here are some of the functions that most likely need to be overridden.
 *   `layout_tests_dir`
     *   This tells the port where to look for all the and everything associated
         with them such as resources files.
-    *   By default it returns absolute path to the webkit tests.
+    *   By default it returns the absolute path to the layout tests directory.
     *   If you are planning on running something in the chromium src/ directory,
         there are helper functions to allow you to return a path relative to the
         base of the chromium src directory.

docs/layout_tests_linux.md

@@ -10,8 +10,7 @@
         `src/third_party/WebKit/LayoutTests/fast/`.
 1.  When the tests finish, any unexpected results should be displayed.
 
-See
-[Running WebKit Layout Tests](http://dev.chromium.org/developers/testing/webkit-layout-tests)
+See [Layout Tests](testing/layout_tests.md)
 for full documentation about set up and available options.
 
 ## Pixel Tests

media/tools/layout_tests/bug.py

@@ -27,9 +27,8 @@ def __init__(self, bug_modifier):
 
     Args:
       bug_modifier: a string representing a bug modifier. According to
-        http://www.chromium.org/developers/testing/webkit-layout-tests/\
-        testexpectations
-        Bug identifiers are of the form "webkit.org/b/12345", "crbug.com/12345",
+        //docs/testing/layout_test_expectations.md
+        bug identifiers are of the form "webkit.org/b/12345", "crbug.com/12345",
          "code.google.com/p/v8/issues/detail?id=12345" or "Bug(username)"
     """
     match = re.match('Bug\((\w+)\)$', bug_modifier)

media/tools/layout_tests/test_expectations.py

@@ -13,8 +13,8 @@
 DEFAULT_TEST_EXPECTATIONS_LOCATION = (
     'http://src.chromium.org/blink/trunk/LayoutTests/TestExpectations')
 
-# The following is from test expectation syntax. The detail can be found in
-# http://www.chromium.org/developers/testing/webkit-layout-tests#TOC-Test-Expectations
+# The following is from test expectation syntax.
+# See: //docs/testing/layout_test_expectations.md
 # <decision> ::== [SKIP] [WONTFIX] [SLOW]
 DECISION_NAMES = ['SKIP', 'WONTFIX', 'SLOW']
 # <config> ::== RELEASE | DEBUG

testing/android/docs/README.md

@@ -12,7 +12,7 @@
     - [... run a gtest?](/testing/android/docs/todo.md)
     - [... run an instrumentation test?](/testing/android/docs/todo.md)
     - [... run a Robolectric test?](/testing/android/docs/todo.md)
-    - [... run the blink layout tests?](https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tests)
+    - [... run the blink layout tests?](/testing/layout_tests.md)
     - [... run a telemetry test?](/testing/android/docs/todo.md)
   - **miscellaneous**
     - [... use code coverage for Java tests?](/build/android/docs/coverage.md)

third_party/WebKit/LayoutTests/SlowTests

@@ -1,4 +1,5 @@
-# See http://www.chromium.org/developers/testing/webkit-layout-tests/testexpectations for more information on this file.
+# See //docs/testing/layout_test_expectations.md
+# for more information on this file.
 
 # This file should only mark tests as Slow. If they are failing in some other way, that listing should be in TestExpectations.
 # Lines listed in both files will have the *union* of the expectations.