debug-execution

Browser debug execution captures DOM snapshots, screenshots, console logs, and network diagnostics automatically as you navigate and interact with a web application. Run debug-execution after preparing a debug-plan to collect a structured evidence bundle organized for validation and reporting.

Chrome DevTools debugging automates navigation to a URL, baseline DOM and visual capture, interaction loops (click, fill, hover, key press), and outcome validation. Each step collects evidence and compares results against expected outcomes to verify functionality.

Yes. Debug execution validates each interaction step against specified expectations, collecting console and network diagnostics alongside evidence. Results are packaged in a comprehensive validation report ready for analysis and documentation.

Yes. Debug execution works from a prepared debug-plan that defines the target URL and interaction sequence. Generate the debug-plan separately, then pass it to debug-execution to collect evidence and validate outcomes.

Debug execution captures the mismatch in its validation report, including DOM state, screenshot, and diagnostic logs. The structured evidence bundle documents what occurred versus what was expected, supporting root-cause analysis.

Console and network diagnostics are captured automatically as part of the evidence bundle during each interaction step. They're included in the comprehensive report alongside DOM snapshots and screenshots for full debugging context.