Changelog

What shipped recently across the TestRelic SDKs, Cloud Platform, MCP server, and CLI.

September 2026


CLI·

A Planner you can follow, and telemetry that tells the truth

  • Planner is re-navigated around one journey. A progress spine — Intake · Criteria · Build · Run · Sign-off — sits on every plan screen, and one status header carries the verdict counts plus a single next-action button that rewrites itself as you go (Build 3 tests → Run 12 → Sign off). Eight named screens collapse into one visible path; the verdict rules and the vocabulary are unchanged. See Planner.
  • Playwright projects now get the SDK fixture wired automatically. Navigations, network requests and console logs are collected by the fixture your specs import — not by the reporter — so a project that was only reporter-wired streamed those three empty while Studio said they were flowing. A run now repairs the import the way it already repairs the config.
  • Before a signed-in run uploads anything, Studio states what that framework's SDK actually captures, per framework rather than one generic sentence — Python Playwright, pytest, Appium, Maestro and evals each capture a different set, and each now says its own.
  • A plan's share sheet previews the host you are actually signed in to. Until the link exists, the row says it is created on publish instead of offering a URL that leads nowhere.
  • Cloud mode gets its Artifacts shelf back, and separates agent chats from plain chat.

Released as CLI v0.101.0 and v0.102.0.

August 2026


CLI·

Code and Cloud, side by side — and an Artifacts shelf that belongs to your account

  • Studio's two tabs now name the work instead of the network. Code lists the agent sessions on this computer, Cloud the Ask AI chats on your account — so a chat you started on another device finally appears here. A Cloud chat can't run on its own; it hands the ask to Code with your draft carried over and seeded, never sent for you.
  • Artifacts moved out of the single run and into the account: searchable, filterable, pinnable against a storage trim that no longer happens in silence, and exportable as PDF, PNG, Markdown, HTML or JSON. Drill-downs inside a document open Studio's own run and test screens — and images inside an artifact render at all now.
  • The three places that talk about uploading stop contradicting each other. Uploading follows your sign-in, runs an agent started upload too, and a run card now distinguishes "uploading was declined" from "nobody promised either way" instead of offering to switch on something already on.
  • The Reporter pane stops looping: its sign-in button no longer signs you out, the same sentence no longer appears twice in two colours, and the one thing that actually clears the failure is visible again.
  • Studio notices when a newer reporter has been published than the one your project has installed, and stays quiet when the check itself fails rather than crying "update available" at a bad network.

Released as CLI v0.96.0 through v0.100.0.

CLI·

Testing → Planner: plan a release, build tests from it, run, prove, share

  • 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.

Playwright SDK·

Playwright trace uploads, fixed — the artifact that mattered most wasn't reaching the cloud

  • 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).

Cloud Platform·

Session Workspace: the right test's video, and a timeline scaled to it

  • 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.

Cloud Platform·

Infrastructure: bring your own cloud, grid, or CI pipeline

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.

Cloud Platform·

Performance Testing: upload k6 and JMeter runs, get pass/fail service levels

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.