Sessions & Artifacts
Everything a run captures — session video, per-test recordings, console, network, and driver logs — plus the live view and session detail page.
Sessions & Artifacts
Every Automate run becomes a session on your dashboard. Sessions capture rich artifacts automatically — no flags to flip and no code to add — so a failed CI run is something you can watch and inspect, not just a red exit code.
Open a session at Automate → Sessions and click any row for its detail page.
What every run captures
| Artifact | Format | Coverage |
|---|---|---|
| Session recording | MP4 (H.264) | All four browsers |
| Per-test recording | MP4 slice between test hooks | All four browsers |
| Browser console | newline-delimited JSON | Chrome, Edge, Firefox 113+ |
| Network requests | newline-delimited JSON | Chrome, Edge, Firefox 129+ |
| Driver diagnostics | newline-delimited JSON | All four browsers |
| Test output | newline-delimited JSON | Emitted via testkase_action: log |
All capture flags default to on. Set any of recording, console, network, or driver to false under testkase:options to opt out.
Video & per-test recordings
Recording is always on for headed sessions — the agent records the full session as one MP4 and uploads it when the session ends. No REC button, no flag.
On the session detail page:
- The player plays the whole recording by default.
- Clicking a test in the left rail seeks the playhead to that test's start and pauses at its end — you jump straight to the moment a test failed.
Per-test slices are created when your test code emits testkase-name= (start) and testkase-status= (end) hooks. Without those hooks you still get the full session-level recording; the per-test slices simply aren't created. See Selenium → per-test metadata.
Headless sessions (testkase:options.headless = true) are not recorded — there's no desktop to capture.
Console, network & driver logs
How console and network capture work depends on the browser's protocol:
- Chrome / Edge expose Chrome DevTools Protocol — the agent taps it to forward console and network events with zero code from you.
- Firefox uses W3C WebDriver BiDi. Console works from Firefox 113+; network capture from Firefox 129+ (older majors still run, but their Network tab stays empty, with in-app copy explaining the cutoff).
- Safari has neither protocol, so console and network stay dark — matching BrowserStack and LambdaTest.
Driver diagnostics are captured for all four browsers (verbose logs for the Chromium drivers and geckodriver; stderr for safaridriver).
Live view
Open a session's detail page while your test is running to watch it live — the Live tab shows a WebRTC stream of the in-VM browser, and logs, network, and driver events tick into their tabs in real time from the moment you open the tab.
Events that fired before you opened the tab aren't replayed in the live tail — but they're all in the full transcript after the session ends. The post-session transcript is authoritative and includes every captured event, regardless of when you started watching. CI runs that never open the dashboard pay zero live-streaming overhead.
Builds & grouping
Set testkase:options.build to a CI run ID or commit SHA and every session in that run rolls up under one named build. Use name for a per-session label and tags for free-form filtering on the session list.
When artifacts are available
Artifacts upload at session end and appear on the detail page once processing finishes. Captures that landed before an automatic timeout cut-off are preserved — the video, logs, and test output from the active window are all available even if a session was reaped. See Reference → session timeouts.