Release notes··5 updates
5 updates shipped on September 29, 2026.
Highlight
Featured this release
With several test inboxes in a project, the agent opens the one it needs.
The agent knows the email addresses and SMS number configured for your project and opens the inbox it needs, filtered to that address. Flows that send verification codes to more than one address get the right code.
More on this: authentication testing, SaaS onboarding testing and AI testing with QA.tech.
Update 02 of 05
docs.qa.tech has new guides for test data, the SMS inbox, copy and paste, responsiveness and cross-application tests.
The regression and PR testing CI pages on docs.qa.tech are now self-contained, including how to find short IDs. GitHub App and GitHub Actions share one GitHub integrations page, and the new Test data guide is first under Build Tests.
More on this: automated regression testing and PR testing.
Update 03 of 05
Library rows on the assistant knowledge page open in the same drawer as rules, skills and memories.
Under Settings → Knowledge → Assistant, click a Library row to see its status, content, source, pages and repository details. Edit it from the row menu or the drawer, and delete it from the drawer.
More on this: product overview and QA testers.
Update 04 of 05
The API page shows your project short ID and pre-fills it in the curl examples.
Settings → Integrations → API shows your project's short ID as a copyable chip, and the run, create-test and change-review curl examples come pre-filled with it. Project settings show the same chip under the project name, and test plan short IDs from long names are capped at 48 characters, with the full value in a tooltip.
More on this: API testing and PR and CI/CD testing.
Update 05 of 05
The spend limit form shows the billing period and commit it covers, and owners and admins get an email at the hard limit.
Under Settings → Billing, the spend limit form shows the billing period the soft and hard limits apply to, with dates, and the prepaid or postpaid commit that covers it. The same amounts carry into the next period. When the hard limit is reached, organization owners and admins get an email explaining that new runs are paused until the period ends or the limit is raised, and that runs in progress can finish.
More on this: CTOs and subscription billing testing.
QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.