Release notes··3 updates

PR triage, a denser coverage map, and faster navigation

3 updates shipped on October 8, 2026.

  1. Highlight

    Featured this release

    PR triage skips changes that can't affect your tests

    QA.tech can skip PR reviews for changes like READMEs, CI config and build tooling.

    With PR triage on, a quick check runs before the review agent starts. Docs, infrastructure, manifest, CI and build-tooling changes are skipped; user-facing UI, the backend behind it and API-testable changes are still reviewed. New projects and new GitHub integrations start with triage on.

    Edit the "PR triage prompt" under the GitHub integration settings to fit your repo. The Review column in the pull requests list shows "Triage blocked" with the reason in a tooltip.

    More on this: PR testing, PR and CI/CD testing, the PR testing docs and what to test on every PR.

    # Direct link

  2. Update 02 of 03

    A denser coverage map

    The coverage map draws up to 160 pages and 32 actions per page.

    Busy pages no longer look nearly empty. The map samples up to 32 actions per page while keeping the tested/untested mix in line with the page's real ratio, and each card reads like "8 tested of 250", noting how many are shown when the map is a sample.

    More on this: exploratory testing and dashboard testing.

    # Direct link

  3. Update 03 of 03

    Faster project and organization navigation

    Switching between projects, organizations and their pages paints right away.

    The page layout appears immediately while your data loads in, and sidebar, settings and new-chat links prefetch their destinations. Results and pull request pages show a single loading state.

    More on this: product overview and QA testers.

    # Direct link

Your team moves fast. Can your testing keep up?

QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.

Get a demo