Skip to main content

The Trace Viewer

Every run's report page has a Replay panel for a quick, step-by-step pass over what happened. For debugging something deeper than "which step failed", each run also has a dedicated Trace page: the full network activity and a reconstruction of the page's DOM, per step.

Opening it​

From a run's report page, click Open full trace → in the Replay panel's toolbar. This works the same way on a public shared report, so anyone you've shared a report with can dig into the trace too, not just you.

Layout​

The left column lists every step in the run, numbered with its action type and target description. Selecting a step loads that step's data into the right column, which has two tabs:

Network​

Every request and response VeriWasp's browser made while that step ran, in a sortable table: method, URL, status, resource type, size, and duration. Click any column header to sort by it, or use the filter box above the table to narrow it down by URL or method (handy for finding, say, every call to your own /api/ routes on a page that also loads a dozen third-party scripts and trackers).

Click a row to expand it and see the full request and response headers. If a request or response had a body VeriWasp captured, a View request body / View response body link opens it in a new tab. Bodies are capped at 5MB each; a body larger than that is truncated (marked as such next to the link) rather than dropped entirely.

DOM snapshot​

A reconstruction of the page's actual DOM and computed styles at that instant, shown before and after the step ran, side by side. This is a real reconstruction, not a screenshot, so images and fonts loaded from the target site's own origin may not render inside it (the reconstruction is served sandboxed, with no access back to the original site). If a snapshot looks blank at first, scroll within its frame: a real page's tall header, nav bar, or ad slot above the fold is a common reason the interesting content isn't visible until you scroll down.

When to use this instead of Replay​

Replay is built for a fast read: did this step pass, and if not, what did the page look like right before and after. The trace viewer is for going a level deeper, when you need to know exactly which network call failed or timed out, inspect a request's actual payload, or compare the DOM structure VeriWasp actually saw against what you expected, not just a screenshot of it.