Breakpoints and stepping in browser DevTools
A marker on a line in browser DevTools that pauses the program there, so you can step through the code line by line and watch the variables change.
Understanding Breakpoints and stepping in browser DevTools in ACARA Digital Technologies Years 9–10
What it does: The debugger statement placed before console.log pauses the program on that line when DevTools is open. It does the same job as a breakpoint. Step over runs the function call as a single step. Step into would take you inside the function's code. Add something like total to Watch and you can see how its value changes after each step. The correct form is debugger; because it is a keyword. Adding brackets makes JavaScript treat it as a function call, which fails.
Common mistakes: Declaring a variable needs the single = assignment operator. == is a comparison, so this line is a syntax error. It should be let total = 0; so the Watch panel can track total. The keyword is misspelled. It must be function, otherwise the code never runs and the debugger statement is never reached.
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 710–727) and word search (Modules 710–742).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
breakpointFill in the Blanks
Spot the Error
Student with a class code? Join your class →