Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(173)

Side by Side Diff: content/browser/debugger/manual_tests/debugger-step-on-for-statements.html

Issue 11630004: DevTools: rename debugger/ to devtools/, move DevTools files into content/renderer/devtools. (Closed) Base URL: http://git.chromium.org/chromium/src.git@master
Patch Set: For landing Created 8 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
(Empty)
1 <script src="resources/loop-statements.js"></script>
2 <script>
3 function runFor()
4 {
5 /* place breakpoint on next line and click continue */ debugger;
6 for (initialize(); condition(); increment())
7 statement();
8 }
9 </script>
10 <p>To test, open the DevTools (Ctrl+Shift+I) and reload the page.
11 <br><br>
12 Before running the tests please perform the following:
13 Make sure the execution is not paused in the debugger.<br>
14 Click the button and when the debugger breaks, set a breakpoint on the first lin e in the loop
15 (as indicated by the comment), and click continue.<br>
16 The debugger should stop at the beggining of the loop.<br>
17 The above actions should be performed before <b>each</b> of the following tests. </p>
18 <br><br>
19 <input type="button" value="run for" onclick="runFor()"/>
20 <br><br>
21 TEST 1: Click 'continue'. Execution should continue without stopping on the loop breakpoint again.<br>
22 TEST 2: Click 'Step over'. Debugger should step inside the loop to the next stat ement line.<br>
23 TEST 3: Click 'Step into'. Debugger should step into 'initialize' function. Clic k 'Step into' until
24 outside of the 'initialize' function - debugger should enter the 'condition' fun ction.<br>
25 function.<br>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698