Console errors in the trace, environment filters, and a POC setup checklist

Highlight
Featured this release
The testing agent reads browser console errors
The agent can check the browser console during a run and quote the exact error line back in the trace.
During a run the agent can look in the browser console for errors, warnings or logs matching a pattern, and quotes the exact line it found – including uncaught exceptions that never print through normal console handlers.

Each console check gets its own tab in the run trace with the message, its level and the source location, so a broken library version or a failed request shows up as evidence instead of an unexplained failure. Available to every organization.

More on this: web testing and testing AI-generated code.
# Direct link
Update 02 of 07
Chat History shows just your conversations
History groups chats by recency, adds title search, and keeps review threads from crowding out real conversations.
History now groups conversations by Today, Yesterday, Previous 7 Days and Older, and you can search them by title. The Mine and Everyone toggle still switches between your chats and your team's.

New chats appear in the list immediately, and "Load more" pages back through older conversations.

More on this: what QA.tech does and exploratory testing.
# Direct link
Update 03 of 07
Chat-started runs stay out of Results by default
Runs kicked off from chat no longer sit in the project's Results list – one checkbox brings them back.
Results now shows the runs you plan around: test plan, manual, scheduled, API and CI runs. Quick runs started from a chat are hidden, so the list reads as your project's real test history.

A "Results started from chat" checkbox under Filters brings them back whenever you want them.

More on this: web testing and automated regression testing.
# Direct link
Update 04 of 07
Filter Results and test plan runs by environment
Results and each test plan's Recent Results tab now have an Environments filter.
Open Results, then Filters, then Environments to narrow the run list to one or more environments. It combines with the existing Test Plans filter and stays in the URL, so a filtered view is shareable.

The same filter sits on a test plan's Recent Results tab, and "See all" carries your selection into the full Results view.

More on this: multi-environment testing and what CTOs track.
# Direct link
Update 05 of 07
New docs for GitHub Deployments and PR previews
A configuration guide shows how to publish deployment records so QA.tech waits for the right preview before testing.
The docs now cover publishing GitHub deployment records from your workflows, with the required fields and environment mapping, so QA.tech knows when a pull request preview is live and opens the right URL. You will find it under Configuration, GitHub Deployments, with recipes for GitHub Actions and links from the GitHub App setup and CI/CD guides.

It also corrects earlier guidance: the preview URL belongs in environment_url, not target_url, and log_url is for the workflow run link.

More on this: pull request testing and PR and CI/CD testing.
# Direct link
Update 06 of 07
A POC setup checklist in the docs
A step-by-step checklist for getting a proof of concept running, for both web and mobile.
The new checklist under Get Started walks through everything a first project needs: network and WAF allowlisting, authentication, email inbox access, test data, crawl setup, parallel runs, optional CI/CD, and a final smoke test.

It covers both web and mobile applications, and is linked from the guide on creating tests.

More on this: web testing and mobile testing.
# Direct link
Update 07 of 07
Search and bulk actions for assistant memories
The Memories table now has search, multi-select and one-click batch delete.
Memories under Settings, Knowledge, Assistant now render in the same table used for the Library: a search box to filter, checkboxes with select-all, and a row menu for a memory's full details.

Select several memories and delete them in one action instead of one at a time.

More on this: what QA.tech does and AI test generation.
# Direct link

The testing agent reads browser console errors

Chat History shows just your conversations

Chat-started runs stay out of Results by default

Filter Results and test plan runs by environment

New docs for GitHub Deployments and PR previews

A POC setup checklist in the docs

Search and bulk actions for assistant memories

Your team moves fast. Can your testing keep up?