Skip to main content

Reading results

The bottom panel has six tabs, populated as a run executes:

Events​

Every step with its timing and pass/fail status; double-click a row to edit it.

The Events tab — every step with its type, target and timing

Console​

Page-side console output, stamped with the step it occurred on and colored by level (LOG / INFO / WARN / ERROR).

The Console tab — page console output stamped with the step and colored by level

Network​

A familiar request inspector: filter chips (All · Fetch/XHR · Doc · JS · CSS · Img · Font · Media · WS · Other) plus a URL search. Each request shows step, method, status, name, type, size and time; click one for Headers / Payload / Response / Timing. The ◉ Mocked chip switches to the recorded snapshot.

The Network tab — DevTools-style filter chips and request table

Summary​

Pass/fail counts, slowest step, total duration, and the failure screenshot if the run stopped — plus Share run to export the whole run (Share a run).

The Summary tab — pass/fail counts, duration, progress bar and slowest step

Timeline​

A YouTube-style scrubber over time-scaled bars (colored by event type); hover for a thumbnail, click to jump to that step.

The Timeline tab — a scrubber over time-scaled bars; hover for a thumbnail, click to jump

Results stay put​

A run's results — the step outcomes, the console, the network table, the summary and the timeline screenshots — survive switching away from the session. Open another file in the explorer, come back, and the last run is still there, exactly as you left it.

They are replaced when you run that session again, and not before. Nothing is cleared by switching, closing a panel, or reopening a project.

Results also survive restarting Trq: they are written under .trq/runs/ in the project, one file per session, and read back when you reopen it. That folder is gitignored for you.

note

The last run of up to 12 sessions is kept. Beyond that, the least recently run is dropped — the results are a convenience, not an archive. For a record that lasts, use the HTML report a CLI run writes.

When a result no longer matches​

Editing a session invalidates its retained result: step numbers move when steps are added, removed or reordered, so a report pinned to the old numbering would point at the wrong rows. Trq notices and marks the result stale rather than showing you something that silently misreads.

Elements​

A live DOM tree of the page (a familiar Elements-style view) with VS Code syntax colors — handy for checking selectors and structure. The inspect button highlights the element under the cursor.

The Elements tab — a live DOM tree of the page