Guides
Debugging Failures
When a check fails, you need to know why, where, and how it happened. SupaGuard provides high-fidelity "Deep Debugging Traces" to answer these questions instantly.
The Debugging Dashboard
Clicking on any failure in the SupaGuard dashboard opens the Incident Review. This view consolidates three critical sources of truth:
1. Video Recording
Watch exactly what happened during the test execution.
- Why it's useful: Spot visual bugs, layout shifts, or modal popups that obscured a button.
- Control: You can pause, scrub, and change playback speed.
2. Network Trace (HAR)
Inspect every HTTP request made during the session.
- Why it's useful: Identify if a specific API call failed (e.g., a
500error from/api/login) or if a large asset slowed down the page load. - Filter: You can filter by request type (XHR, Image, CSS, etc.).
3. Playwright Trace
Step-by-step execution path of the test script.
- Why it's useful: pinpoint the exact line of code where the assertion failed.
- Context: See "Before" and "After" snapshots for every action (click, fill, navigate).
Common Failure Scenarios
"Element not found"
- Symptom: The test timed out waiting for a button.
- Fix: Watch the video. Did a popup cover the button? Did the page fail to render? If the UI changed, update your selector.
"Timeout exceeded"
- Symptom: The page took too long to load.
- Fix: Check the Network tab. Look for slow API calls or massive images that blocked the load event.
"Assertion failed"
- Symptom: You expected "Welcome User" but got "Login Failed".
- Fix: The script worked, but the app logic failed. This is a genuine bug in your application!