@@ -37,7 +37,7 @@ reference for full documentation.
37
37
38
38
The latest [ Node.js] ( https://nodejs.org/en/ ) provides native async/await, which
39
39
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
41
41
use chrome development tool and chrome inspector together to debug the new
42
42
tests, which will give a nicer debugging experience.
43
43
@@ -48,7 +48,7 @@ inspector and the debugging process is almost the same.
48
48
49
49
We have a simple example to show how to debug async/await in test. You can find
50
50
the whole example in
51
- [ here] ( .. /debugging/async_await.js)
51
+ [ here] ( /debugging/async_await.js )
52
52
53
53
- Add “debugger” keyword to the test case that we want to debug.
54
54
@@ -78,23 +78,23 @@ the whole example in
78
78
- Open chrome inspector: Enter " chrome://inspect/#devices" in browser, find
79
79
the current running target and click “Inspect”
80
80
81
- ! [screenshot](. / inspector .png )
81
+ ! [screenshot](/ docs / inspector .png )
82
82
83
83
- The test will start and pause at the beginning.
84
84
85
- ! [screenshot](. / firstBreak .png )
85
+ ! [screenshot](/ docs / firstBreak .png )
86
86
87
87
- We can click F8 (resume script execution), and the test will pause at the
88
88
first line that has our “debugger ” keyword . We can then add breakpoints and
89
89
debug tests.
90
90
91
- ! [screenshot](. / breakpoint .png )
91
+ ! [screenshot](/ docs / breakpoint .png )
92
92
93
93
- We can also open chrome development tool on the webdriver controlled browser
94
94
to check the html elements and do some queries while the test execution is
95
95
pausing.
96
96
97
- ! [screenshot](. / chromeDevTool .png )
97
+ ! [screenshot](/ docs / chromeDevTool .png )
98
98
99
99
- Known Issues
100
100
0 commit comments