Release notes··4 updates
4 updates shipped on May 5, 2026.
Update 01 of 04
Runs that span multiple environments no longer drop tests that depend on each other.
When you run a test plan across multiple environments and some tests depend on the output state of other tests (e.g. a login test feeds into a checkout test), the runner used to occasionally drop dependent test cases when reconstructing the run. Fixed. Cross-environment dependency chains are preserved.
Update 02 of 04
Tickets filed to Jira, Linear, Trello and Slack now ship with the actual steps the agent took.
Earlier in April we landed richer Jira tickets that include the test goal, expected result, and the steps the agent took. We've now extended that to Linear (collapsible block), Trello and Slack (compact paragraph), and improved the Jira format to use Atlassian Document Format so the steps render as a proper expandable list rather than plain text.
This is most useful for teams where not every developer has a QA.tech account, or where the issue tracker is the canonical source of truth.
Update 03 of 04
Multi-deployment PRs now run against the right environment instead of guessing.
When a PR triggers multiple deployments (a preview, a Storybook, a marketing site, an API), QA.tech used to pick one and hope. It now respects the GitHub environment mapping you've configured under integration settings. If you've mapped "Preview" to your main app, that's what gets tested. Deployments that aren't mapped to anything (Storybook, docs builds, API-only previews) are skipped instead of falling back to your default app.
If you've ever seen a PR review run against the wrong URL, this is the fix.
Update 04 of 04
Multi-app projects get a proper application filter on the Test Plans page.
Test Plans now has a multi-select Applications filter at the top of the page, with color indicators per application and select-all / clear-all. The filter only appears when a project has more than one application, so single-app projects don't see clutter. We applied the same filter pattern to Configs at the same time, so the Applications dropdown looks and behaves the same wherever you find it.
See how QA.tech agents test your product in a 30-minute demo – and leave with a plan to reclaim those hours.