Skip to content
This repository was archived by the owner on Jul 29, 2024. It is now read-only.

Commit 3b29ee7

Browse files
authored
fix(doc): update links in debugging docs to make it show correctly in the website (#4615)
Change relative directories to absolute directories that start from protractor root.
1 parent 18d06e8 commit 3b29ee7

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

docs/async-await.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ upcoming ES7 feature `async`/`await`.
2020

2121
- If we disable control flow and use async/await to write tests, we can get a
2222
better debugging experience by using [chrome
23-
inspector](./debugging.md#disabled-control-flow)
23+
inspector](/docs/debugging.md#disabled-control-flow)
2424

2525
**How to use native async/await in test**
2626

docs/debugging.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ reference for full documentation.
3737

3838
The latest [Node.js](https://nodejs.org/en/) provides native async/await, which
3939
means we can get stable e2e test easily without using control flow. Furthermore,
40-
if we write our test by using async/await[(how to?)](./async-await.md), we can
40+
if we write our test by using async/await[(how to?)](/docs/async-await.md), we can
4141
use chrome development tool and chrome inspector together to debug the new
4242
tests, which will give a nicer debugging experience.
4343

@@ -48,7 +48,7 @@ inspector and the debugging process is almost the same.
4848

4949
We have a simple example to show how to debug async/await in test. You can find
5050
the whole example in
51-
[here](../debugging/async_await.js)
51+
[here](/debugging/async_await.js)
5252

5353
- Add “debugger” keyword to the test case that we want to debug.
5454

@@ -78,23 +78,23 @@ the whole example in
7878
- Open chrome inspector: Enter "chrome://inspect/#devices" in browser, find
7979
the current running target and click “Inspect”
8080

81-
![screenshot](./inspector.png)
81+
![screenshot](/docs/inspector.png)
8282

8383
- The test will start and pause at the beginning.
8484

85-
![screenshot](./firstBreak.png)
85+
![screenshot](/docs/firstBreak.png)
8686

8787
- We can click F8 (resume script execution), and the test will pause at the
8888
first line that has our “debuggerkeyword. We can then add breakpoints and
8989
debug tests.
9090

91-
![screenshot](./breakpoint.png)
91+
![screenshot](/docs/breakpoint.png)
9292

9393
- We can also open chrome development tool on the webdriver controlled browser
9494
to check the html elements and do some queries while the test execution is
9595
pausing.
9696

97-
![screenshot](./chromeDevTool.png)
97+
![screenshot](/docs/chromeDevTool.png)
9898

9999
- Known Issues
100100

exampleTypescript/asyncAwait/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ to create a breakpoint. Note that sourcemaps don't work in the inspector
2626
in Node v6, but do work in Node v7 (due to https://github.com/nodejs/node/issues/8369).
2727

2828
More detail about how to use [chrome
29-
inspector](../../docs/debugging.md#disabled-control-flow)
29+
inspector](/docs/debugging.md#disabled-control-flow)
3030

3131
More Examples
3232
=============

0 commit comments

Comments
 (0)