Release notes··2 updates

    Smarter error classification and Coverage polish

    2 updates shipped on April 27, 2026.

    1. Update 01 of 02

      Coverage page polish

      Smaller fixes from the first month of Coverage being broadly available.

      A handful of changes off the back of customer feedback after the Coverage GA in April:

      • "Top Gaps" CTA renamed to "Fix in chat" to make it obvious where the action goes.
      • Tightened spacing throughout the Coverage page.
      • Fixed a bug where the coverage progress bar was invisible at very low coverage values.

      # Direct link

    2. Update 02 of 02

      Smarter HTTP error classification

      A 4xx in the network log no longer fails an otherwise-passing test.

      When the agent saw a 4xx or 5xx response in the network log, it sometimes called the run a failure even when the user-visible step had clearly succeeded – common with API tests, with UI tests that pass through a 404 page on their unhappy path, and with apps that intentionally probe failure responses. The Assessment Agent now decides whether a transport-layer error is actually a real failure based on the test goal and what the user actually saw, instead of failing on the first non-200 in the log.

      # Direct link

    Ready to end the QA bottleneck?

    See how QA.tech agents test your product in a 30-minute demo – and leave with a plan to reclaim those hours.

    Get a demo