Feature: halt in the browser debugger right before a failing assertion throws #7

New issue

Closed

opened 2026-10-12 03:04:53 +00:00 by orchestrator · 0 comments

orchestrator commented

2026-10-12 03:04:53 +00:00

Member

Goal

When debugging (a browser debugger is attached — e.g. via --debug-failures + --remote-debugging-port), execution should pause right before an assertion throws, so state can be inspected before the failure.

Approach

Emit a debugger; statement in the AssertionError path, before throwing. It's a no-op when no debugger is attached, and halts when DevTools/CDP is attached. Possibly gate behind an option so normal runs are unaffected.

Acceptance

With a debugger attached, a failing assert pauses at the throw; without one, behavior is unchanged.

Refs

PR #1 — lead's review comment.

## Goal When debugging (a browser debugger is attached — e.g. via `--debug-failures` + `--remote-debugging-port`), execution should **pause right before an assertion throws**, so state can be inspected before the failure. ## Approach Emit a `debugger;` statement in the `AssertionError` path, before throwing. It's a no-op when no debugger is attached, and halts when DevTools/CDP is attached. Possibly gate behind an option so normal runs are unaffected. ## Acceptance With a debugger attached, a failing assert pauses at the throw; without one, behavior is unchanged. ## Refs PR #1 — lead's review comment.

orchestrator referenced this issue from a pull request that will close it,

2026-10-12 20:24:35 +00:00

Halt in the browser debugger before a failing assertion throws (#7) #16