# Risk-sized PR runs, rerun history, and run-finished notifications > 4 updates: PR reviews size their test runs to the risk of the change, Get a browser notification when a run finishes, Move test cases back to Draft from… Source: https://qa.tech/changelog/2026-08-25 --- 4 updates shipped on August 25, 2026. In this release 1. 01[PR reviews size their test runs to the risk of the change](#2026-08-25-pr-reviews-size-runs-to-risk)Highlight 2. 02[Get a browser notification when a run finishes](#2026-08-25-browser-notification-when-run-finishes) 3. 03[Move test cases back to Draft from chat](#2026-08-25-move-tests-back-to-draft-from-chat) 4. 04[Rerun history on the run results list](#2026-08-25-rerun-history-on-results-list) 1. Highlight Featured this release ## PR reviews size their test runs to the risk of the change Instead of a flat 7–12 tests on every pull request, the review agent scales coverage to how risky the change actually is. The [PR review agent](https://qa.tech/product/pr-testing) now scores each pull request's test risk from the change's blast radius, how central the affected flows are and what coverage already exists. Low-risk changes get 1–3 tests instead of 7–12, while high-risk ones get the full 8–12. There is always at least one real test on the primary path, and the review summary carries a one-line note on the risk read and what it covered. It reads as coverage, never as a code-quality judgment, and the pass/fail verdict is unchanged. [\# Direct link](#2026-08-25-pr-reviews-size-runs-to-risk) 2. Update 02 of 04 ## Get a browser notification when a run finishes A bell next to the Running count arms a desktop notification and a chime for the run or test you're watching. Click the bell – on the run results page, a single test result page or the test editor header – and QA.tech asks for browser notification permission once, then remembers it, so later runs are armed without clicking again. The notification fires only when the tab is hidden or the window is unfocused, and its text carries the outcome, for example "17 passed, 1 failed". Clicking it focuses the tab back on the run. For Slack and email, see [notifications](https://docs.qa.tech/core-concepts/notifications). [\# Direct link](#2026-08-25-browser-notification-when-run-finishes) 3. Update 03 of 04 ## Move test cases back to Draft from chat The chat agent could already activate and archive tests; it can now convert Active tests back to Draft too. Ask the [chat agent](https://docs.qa.tech/core-concepts/ai-chat-assistant) to move a test to Draft and it applies the change in place. If other Active tests depend on that one – a login or precondition test, directly or through a chain – the agent names those dependents so you can include them in the same request or change their dependencies first. Activating a Draft test works exactly as before. [\# Direct link](#2026-08-25-move-tests-back-to-draft-from-chat) 4. Update 04 of 04 ## Rerun history on the run results list Every test row carries a badge that opens the full attempt history, with a link to each individual execution. Click the ↻ N badge next to a test in the Results List to see every attempt with its status, duration and whether it was an automatic retry, plus a link straight to that exact execution. Opening an older attempt shows a "Viewing Original run" notice with a "View latest rerun" link back. This brings the results page in line with the rerun history added to the chat panel earlier in August. See [tests and results](https://docs.qa.tech/core-concepts/tests-and-results). [\# Direct link](#2026-08-25-rerun-history-on-results-list) ## 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](https://qa.tech/demo) [QA.tech](https://qa.tech/) SOC 2 Type 2 compliant ![Sensiba SOC 2 Type 2 compliant](https://qa.tech/assets/soc2-type2-badge-DPb1j9VX.png) ### Product - [Platform overview](https://qa.tech/product) - [AI QA Testing](https://qa.tech/ai-qa-testing) - [Web Testing](https://qa.tech/product/web-testing) - [Mobile Testing](https://qa.tech/product/mobile-testing) - [Voice Testing](https://qa.tech/product/voice-testing) - [PR Testing](https://qa.tech/product/pr-testing) - [MCP](https://qa.tech/product/mcp) - [Integrations](https://qa.tech/product/integrations) - [Use cases](https://qa.tech/use-cases) - [Changelog](https://qa.tech/changelog) ### Compare - [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress) - [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright) - [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl) - [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf) - [AI vs Human QA](https://qa.tech/saas) ### Resources - [Docs](https://docs.qa.tech/) - [Blog](https://qa.tech/blog) - [Events](https://qa.tech/events) - [Pricing](https://qa.tech/pricing) - [Case Studies](https://qa.tech/case-studies) ### Company - [About](https://qa.tech/about-us) - [Partnerships](https://qa.tech/partnerships) - [Press](https://qa.tech/press) - [Contact Us](https://qa.tech/contact) - [Privacy Policy](https://qa.tech/privacy-policy) - [Terms of Service](https://trust.qa.tech/resources?s=mb9w4yjb03i3t8bjsq4jx3&name=main-agreement.pdf) - [Security & Compliance](https://trust.qa.tech/) ### Social - [](https://www.linkedin.com/company/qa-tech-ai/) - [](https://x.com/getqatech) - [](https://www.instagram.com/getqatech/) © 2026 QA.tech. All rights reserved