Changelog

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

October 2026


Cloud Platform·

Ask AI artifacts are designed for every width, and session video fills its frame

The default template Ask AI starts each artifact from is now designed for every width, from a share page to the side panel and a phone. Test videos and screenshots embedded in artifacts fit the space they're given.

  • A template for every width. In the default template, stat tiles sit four to a row, two in the side panel and one on a phone, and larger cards take the full width. Charts scale with their card, and wide tables scroll inside their own box with the first column kept in view. Slide decks scale rather than reflow.
  • Long names wrap. Long test names and URLs wrap in every artifact instead of running past the edge.
  • Video fills its frame. An embedded test video takes its height from its width at 16:9, and screenshots at 4:3, instead of sitting in a fixed-height box.
  • Screenshots show one at a time, fitted whole, with Previous screenshot and Next screenshot buttons and a counter. Before, the first image was often cropped.
  • Embeds keep what the artifact asked for: the right test's recording in a run with several, the moment the video should open at, and any step, log level or search narrowing.
  • Cleaner captions. Screenshot captions drop a "Step N:" prefix that never matched the step, and Playwright's failure screenshot reads "At the failure".

See AI Insights & Artifacts.

Cloud Platform·

Ask the billing team from the Billing page

Settings → Billing has a way to reach the billing team without leaving the page. Any member can use it.

  • Billing help in the page header (during a trial, the header shows the trial instead), or Contact billing at the foot of every tab, opens a short form:
    • pick a topic, such as Payment failed, Refund or Tax or billing details;
    • choose the invoice it's about, if it's about one;
    • write your message, and optionally copy someone else.
  • Your account details go with it. Sent with your request lists exactly what's included: the workspace, plan, next invoice, billing details, your three most recent invoice numbers, and who sent it from which tab. Your payment method isn't included.
  • You get a reference (BH-…) and an email copy. Replies come to your email address. The form says to expect them usually within one business day.

Also in this release, the country and state lists in Billing details open next to their fields again. They had been opening at the top-left corner of the page.

Cloud Platform·

Repo Overview leads with release readiness

A repository's Overview tab is redesigned around one question: can this repo ship, and what stands in the way.

  • A readiness verdict opens the page. Ship-ready, Hold or Blocked, with a score out of 100 (ship-ready is 85), a summary written from your measured results, and the latest run. What moves the score lists the work items that would raise it and the score each would reach. Below, the score's four parts (pass rate, stability, critical paths and the share of tests grouped in a module) are drawn against the same line. Ask AI for a fix plan opens Ask AI with a plan request for this repo.
  • Key numbers in one row: pass rate, failing tests, flaky tests with the flake rate, time to feedback (median run time, with p95), time to recover, and runs.
  • Time to feedback measures whole runs. It and the Delivery view's median run had shown a per-test median, such as "2s" for a suite whose runs take minutes.
  • New widgets. Since the last run shows new failures, fixed tests, tests still failing and new tests, against the previous run on the same branch. Work to green ranks what stands between the repo and a green release, with each test's recent runs and the readiness points fixing it would add. Where the time goes shows each suite's share of test time.
  • Pass rate trend shows every day in the window, with days that had no runs left as gaps rather than 0%, plus a target line.
  • Renamed widgets: AI defects is now Root causes, and Most affected pages is now Where failures land.
  • A quieter toolbar. The filters sit behind Filter, and each applied filter shows as a chip you can remove. Customize shows the controls to drag cards, change their width and remove them, and holds Add a widget.
  • Quality and Delivery read as scorecards, with each metric against its target, its trend and a reading.

See Repositories.

Cloud Platform·

Overview settings get their own page, and critical paths count every chosen suite

The Overview's Configure drawer is replaced by an Overview settings page, and the readiness check now reads every suite you've marked as a critical path.

  • Ways in: Overview settings in the Overview's ⋯ menu, Choose critical paths (or Review critical paths) on the readiness band, and Edit targets on the Quality and Delivery scorecards. The page has its own link, and Back to Overview returns you.
  • Sections: Critical user paths, Targets, Scorecard display, Blocking lanes, Data sources (GitHub Actions, Jira, Amplitude and BrowserStack, each with Connect or Manage) and Scheduled reports.
  • See the effect before you save. A preview re-scores readiness and re-grades both scorecards against your draft. Nothing is stored until Save changes, and leaving with unsaved changes asks first.
  • Critical user paths lists every suite with its test count, its pass rate and its latest results, with search and All, Chosen and Failing or flaky filters. Any failing or flaky test in a chosen suite turns the verdict to Blocked. A chosen suite that no test in the window carries is flagged, with Remove.
  • Targets show the current value beside each field.
  • Fixed on large repositories. The readiness check read only the first 100 tests, so with more tests it could say critical paths were "not set" while suites were chosen, and leave those suites' tests out of the score. It now loads every chosen suite's tests. A chosen suite with no tests in the window reads "no tests here".
  • Removed, because they never did anything: the weekly digest and Slack switches (send the Overview with Scheduled reports instead), and CircleCI, Jenkins and LinearB under data sources. Scorecard rows that can't be measured read Not measured yet.

See Repositories.

Cloud Platform·

Settings → Usage moves into Billing

The separate Usage page in Settings is gone. What it showed now lives on Settings → Billing.

  • Usage meters for storage, AI tokens and memory are on Billing → Plan & usage. Day-by-day AI token usage is under Usage history.
  • Value delivered is now a Billing tab, for admins.
  • Old links still work. Bookmarks to Settings → Usage open Billing, and searching Settings for usage or value delivered takes you there.
  • The Ingestion Health tab has been removed.
Cloud Platform·

An unpaid invoice now pauses the account

A workspace now pauses once an invoice it owes is past its due date.

  • What stops: uploads and AI features. Nothing is deleted.
  • Every page says so.
    • An Account Paused banner links to Pay invoice.
    • Billing names the invoice and the date it was due, with a View invoice button.
  • Paying resumes it straight away, once no other invoice that pauses the account is still owed.
  • Add-ons while paused: you keep what you hold, but you can't buy more until the invoice is paid. If the account was paused for another reason, Billing says so, with Contact billing to ask for it to be resumed.

Also in this release, the memory add-on comes in blocks of 1,000 entries, up to 50,000 entries. Blocks of 500 you already hold keep renewing, marked legacy.

See Plans & Billing.

Cloud Platform·

A redesigned Billing page, and AI token usage day by day

Settings → Billing has been redesigned. Its first tab is now Plan & usage, followed by Payment methods, Invoices and Billing details.

  • Plan & usage opens with your plan, its status and renewal date, and the next invoice. The invoice lists the plan and add-ons with a subtotal and total, and says how it will be paid: auto-charged to a saved method, or invoiced to your billing email.

  • Usage meters:

    • Artifact storage shows how much is videos, screenshots, or traces and other files.
    • AI tokens shows where the month is heading. The allowance resets on the 1st at 00:00 UTC.
    • Memory shows retained entries.

    Each meter shows what your plan includes and what add-ons contribute.

  • AI token usage, day by day. Open it from Usage history on the Billing page, or from AI tokens in the header's usage badge. Any member can open it.

    • It shows the month's total, daily average, projected total, busiest day and credit in reserve, as charts or a table.
    • Pick an earlier month to look back. Daily detail starts from this release; for earlier months you get the month's total.
  • Change plan compares plans side by side, monthly or annual. Before you confirm a downgrade, it spells out what changes, such as lower storage and retention, and add-ons ending below Pro.

  • Enterprise workspaces see Limits & retention in place of add-ons.

    • Admins can set the workspace's own caps on storage and monthly AI tokens, and its run retention, within the contract's limits.
    • At a cap, new uploads or AI requests stop, and admins are warned at 80%.
    • Changes to the plan itself go through your contract.

See Plans & Billing.

CLI·

The Cursor engine runs once Cursor is installed and signed in

Studio and the CLI now run the Cursor engine whenever Cursor's CLI is installed and signed in.

  • Windows installs are found, and start. A native install from irm 'https://cursor.com/install?win32=true' | iex is found even when your PATH predates it, and its first message no longer fails to start. The install hint now gives that command, and Studio's engine picker lists Cursor as available.
  • Plan mode works in a new folder. A plan turn in a folder Cursor hasn't trusted used to stop with "Workspace Trust Required". It now runs, on Cursor builds that support --trust.
  • WSL works too, with Cursor installed in ~/.local/bin by its install script.
  • Token usage is counted, cache reads and writes included.
  • New names and overrides. Cursor's newer agent command name is recognised, and TESTRELIC_CURSOR_BIN points TestRelic at a specific Cursor binary.

Released as testrelic-cli 1.5.3.