chromium/src
0
Fork 0
Code Activity

Fix broken links in documentation for writing web tests

Browse Source 
Change-Id: I185fd95debae1b80e578fbf061f076cd490938b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2316866
Reviewed-by: Charlie Reis <creis@chromium.org>
Commit-Queue: Wolfgang Beyer <wolfi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#792165}
This commit is contained in:
Wolfgang Beyer
2020-07-28 06:30:46 +00:00
committed by Commit Bot
parent c1608dd3f4
commit af543d736e
1 changed files with 5 additions and 5 deletions

10
docs/testing/writing_web_tests.md

@@ -226,9 +226,9 @@ other tests that use it, or reading its source code.
For example, the most popular Blink-specific API is `testRunner`, which is For example, the most popular Blink-specific API is `testRunner`, which is
implemented in implemented in
[content/shell/test_runner/test_runner.h](../../content/shell/test_runner/test_runner.h) [content/shell/renderer/web_test/test_runner.h](../../content/shell/renderer/web_test/test_runner.h)
and and
[content/shell/test_runner/test_runner.cc](../../content/shell/test_runner/test_runner.cc). [content/shell/renderer/web_test/test_runner.cc](../../content/shell/renderer/web_test/test_runner.cc).
By skimming the `TestRunnerBindings::Install` method, we learn that the By skimming the `TestRunnerBindings::Install` method, we learn that the
testRunner API is presented by the `.testRunner` etc. objects. Reading the testRunner API is presented by the `.testRunner` etc. objects. Reading the
`TestRunnerBindings::GetObjectTemplateBuilder` method tells us what properties `TestRunnerBindings::GetObjectTemplateBuilder` method tells us what properties
@@ -259,12 +259,12 @@ by tests that stick to Web Platform APIs. The `testharnessreport.js` file in
and uses the `testRunner` API. and uses the `testRunner` API.
*** ***
See the [content/shell/test_runner/](../../content/shell/test_runner/) directory and See the [content/shell/renderer/web_test/](../../content/shell/renderer/web_test/) directory and
[WebKit's LayoutTests guide](https://trac.webkit.org/wiki/Writing%20Layout%20Tests%20for%20DumpRenderTree) [WebKit's LayoutTests guide](https://trac.webkit.org/wiki/Writing%20Layout%20Tests%20for%20DumpRenderTree)
for other useful APIs. For example, `eventSender` for other useful APIs. For example, `eventSender`
([content/shell/test_runner/event_sender.h](../../content/shell/test_runner/event_sender.h) ([content/shell/renderer/web_test/event_sender.h](../../content/shell/renderer/web_test/event_sender.h)
and and
[content/shell/test_runner/event_sender.cc](../../content/shell/test_runner/event_sender.cc)) [content/shell/renderer/web_test/event_sender.cc](../../content/shell/renderer/web_test/event_sender.cc))
has methods that simulate events input such as keyboard / mouse input and has methods that simulate events input such as keyboard / mouse input and
drag-and-drop. drag-and-drop.