Release notes··12 updates
12 updates shipped on May 27, 2026.
Update 01 of 12
Routes and cookies were tightened as part of a broader security review.
OAuth integration endpoints now enforce stricter access controls, closing a path where one account could interfere with another's active connection. Session cookie protections were also improved.
Update 02 of 12
Conversations started through the public API now show the correct owner instead of a generic system account.
Conversations started through the public API now show the correct owner instead of a generic system account. When a conversation is created via the API using an API key, it is now attributed to the user who owns that key. This is reflected in the created_by field on conversations and is visible in audit history.
Update 03 of 12
Instead of stalling silently, change review now surfaces a clear message when a fetch fails.
If a change review is triggered on a page behind authentication or an otherwise unreachable URL, it now shows an explicit error rather than leaving the UI in an unclear state.
Update 04 of 12
Test cases suggested by the chat agent now execute together instead of as separate test runs.
When you asked the chat agent to run a set of suggested test cases, they previously spawned as multiple independent runs – one per group. They now run as a single coordinated test run, making results easier to review in one place.
Update 05 of 12
The chat view now loads test run sessions correctly when browsing a test suite.
In some cases, opening a test suite from chat would show no sessions even when runs existed. The underlying fetch is now accurate and sessions appear as expected.
Update 06 of 12
Test failures now correctly generate issues again.
A regression caused issues to stop being created when test runs completed. The trigger that creates issues from failed tests has been restored.
Update 07 of 12
Some new sign-ups hit an error during onboarding. Fixed.
A query error introduced with recent changes caused the onboarding flow to fail for some users. The underlying issue has been corrected.
Update 08 of 12
Verify your domain and let new teammates auto-join your organization on sign-in – no invitation required.
Teams can now verify their domain and have new teammates auto-join on sign-in – no invitation required. Under Settings → Authentication, you can add your organization's domain (e.g. company.com) and prove ownership with a DNS TXT record at _qatech-verification.<yourdomain>. Once the record resolves, anyone who signs in with a matching email address is automatically added to your organization. Public email providers (Gmail, Outlook, and similar) are blocked from this flow. The domain management screen shows verification status and the exact DNS record to add.
Update 09 of 12
A new outbound IP has been added to QA.tech's published IP list. Refresh your allowlist.
A new outbound IP has been added to QA.tech's published IP list. If your app restricts inbound traffic by IP, refresh your allowlist from the canonical source: /.well-known/qatech-ips.json. The up-to-date list is always available there.
Update 10 of 12
Test runs against preview platforms with an auth gate no longer stall at the gate.
Testing apps on preview platforms that gate URLs behind an authentication screen no longer stalls at that gate. QA.tech now automatically handles the bypass for known preview-deployment patterns, so test runs proceed past the preview screen without manual workarounds.
Update 11 of 12
Organizations can now create teams and assign members to them from Settings.
A new Teams section in organization settings lets you group members into named teams. From the "Edit member" flow you can assign or remove team memberships directly. Teams are also available as context in the chat agent, so you can scope conversations and test runs to a specific team.
Update 12 of 12
The agent can now match descriptions of how something looks to actual screenshots of your site.
When generating or running tests, the agent can now locate elements using visual descriptions – "the eye icon", "the blue submit button" – by matching them against screenshots captured during site crawls. This improves test accuracy on elements that lack clear accessible labels.
See how QA.tech agents test your product in a 30-minute demo – and leave with a plan to reclaim those hours.