Release notes··4 updates

Environments for API-created tests, tested nodes on the coverage map, and contract-aware billing

4 updates shipped on October 7, 2026.

  1. Highlight

    Featured this release

    Set the environment when creating test cases through the API

    POST /v1/test-cases and the MCP create_test_case tool take an optional environment for the first run.

    Pass environment – for example { "url": "https://my-preview.example.com" } – and the first run of a new test targets that preview or tunnel URL instead of the default environment. It applies to the first run only and isn't stored on the test case. URLs must be http(s).

    Useful for coding agents that write a test and want it checked against their own branch – see agentic testing.

    More on this: MCP and coding agents, API testing and testing AI-generated code.

    # Direct link

  2. Update 02 of 04

    Billing page follows your contract

    Invoices and Commits & Credits appear for every member of an organization with a contract.

    Under Settings → Billing, the Invoices and Commits & Credits tabs show whenever your organization has a contract, including ended ones. Budget & Spending Alerts and Spend Limits are editable for owners and admins when they apply, and usage rows use readable labels like "Chromium" and "Mobile Builds".

    More on this: pricing and CTOs.

    # Direct link

  3. Update 03 of 04

    Coverage map shows what's tested

    Tested actions and pages light up on the Coverage map.

    Actions touched by a test, and pages with at least half their actions covered, are filled near-white, while untested nodes keep their application color. A "Tested" legend sits bottom-left, the info panel gets a "Tested" row, and side-panel thumbnails center on the action.

    More on this: automated regression testing, CTOs and why 100% coverage isn't the goal.

    # Direct link

  4. Update 04 of 04

    Jump to the latest run from Automations

    The Last Run date on the Automations page links straight to the latest run.

    Chat automations open the conversation and test-plan automations open the run result. The date stays plain text until a run has been recorded.

    More on this: smoke testing and automated regression testing.

    # Direct link

Your team moves fast. Can your testing keep up?

QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.

Get a demo