Practise the standard verbs for debugging effectively with browser DevTools.
0 / 5 completed
1 / 5
Fill in: 'We ___ a breakpoint directly in the Sources panel rather than sprinkling console.log statements everywhere, so execution actually pauses exactly where we need it to.'
We 'set a breakpoint' — the standard, established DevTools collocation for pausing execution at a chosen line. The other options aren't the recognised term here.
2 / 5
Fill in: 'Debugging purely with scattered console.log calls instead of the debugger can ___ the actual call stack at the moment of failure completely invisible.'
We say log-only debugging will 'leave' the call stack invisible — the standard, natural collocation for the resulting blind spot. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the Network tab closely during a failing request, since the actual response body and status code usually explain the bug faster than any client-side log.'
We 'inspect a tab' — the standard, simple collocation for examining request details in DevTools. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a conditional breakpoint on a loop that only fails on one specific iteration, so execution doesn't pause a hundred times before reaching the case we actually care about.'
We 'add a breakpoint' — the standard, simple collocation for inserting a targeted pause point. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ memory snapshots before and after a suspected leak in the Memory panel, so a growing heap is a measured comparison rather than just a hunch.'
We 'compare snapshots' — the standard, simple collocation for contrasting memory state across two points in time. The other options are less idiomatic here.