Changelog

• Studio can now plan what a release promises, build tests from that plan, run them, prove it, and share the result — identical in Local and Cloud mode.
• Evidence links now survive a test ID changing under them.
• A trace alone now counts as evidence — a run isn't "missing artifacts" just because it has no screenshot or video.
• A cloud run now records its own upload verdict, and the run panel warns when a project would upload to a different environment than the one you're signed in to.

Released as CLI v0.94.0.

• Projects running trace: 'on' wrote trace.zip to disk but never uploaded it — only screenshots and video were collected. Fixed hardest exactly where it mattered most: a beforeEach failure has no screenshot worth having, and a pure timeout previously reached the cloud with no artifact at all.
• Traces are now collected, classified, and uploaded alongside screenshots and video.

Released as @testrelic/playwright-analytics 2.13.0. Note for existing users: every project already running trace: 'on' will start uploading trace archives — they're the largest of the three artifact kinds (~900KB in verified runs).

• Fixed: selecting a test with no video of its own could show another test's recording instead of an empty state. Fixed in both the Session Workspace and the Ask AI embedded workspace.
• Fixed: the recording's timeline axis was scaled to the run's total duration instead of the selected test's, so a 30-second test inside a 4-minute run rendered crushed into roughly the first 12% of the scrubber.

See Session Workspace for how test evidence is organized.

Where your tests run is now a workspace setting instead of a file on one person's laptop. The new Infrastructure console — now in the header nav, right after Test Runs — manages three kinds of execution target: your own AWS / Azure / GCP machines, a device grid (BrowserStack, TestMu AI), or your own CI pipeline (GitHub Actions, GitLab CI, including self-managed GitLab). A CI target is treated honestly: connecting one provisions nothing, and TestRelic never estimates your CI cost.

See Infrastructure for the full breakdown. Bring-your-own execution targets are a Pro-and-above entitlement, rolling out gradually.

Load testing joins TestRelic as a first-class run type. Upload results from k6 or JMeter and get one workspace regardless of which tool produced the run: synchronized concurrency, throughput, latency, and error-rate lanes, a failure-first playhead, and repo-level service levels that gate or warn on a threshold breach.

See Performance Testing for setup and the full workspace walkthrough.

Ask AI's artifacts — like generated slide decks — render live in the conversation again. Valid decks were being rejected and failed to render.

• The API console now follows a test's actual call flow, instead of a flat request list.
• The terminal is rebuilt around discrete command blocks.
• Every signed-in run now uploads automatically, and a new Test-runs history view tracks them.

• Switching engines mid-conversation no longer loses your chat history.
• Agent-run Git actions now go through a visible approval surface instead of running silently.
• Memory gets a read-side UI: a chat memory strip, and the Memory view split into Brief, Suggested, and Settings.
• Also fixed: oversized run commands, run history now behaves as a filter, and header window-control buttons that weren't responding.