# Post-run AI analysis, geo-routing, and self-describing MCP tools

> 5 updates: Post-run AI analysis and automatic reruns, Bitrise CI/CD integration guide, Test from specific countries using geo-location routing, MCP tools…

Source: https://qa.tech/changelog/2026-06-16

---
5 updates shipped on June 16, 2026.

In this release

1.  01[Post-run AI analysis and automatic reruns](#2026-06-16-post-run-ai-analysis-and-automatic-reruns)Highlight
2.  02[Bitrise CI/CD integration guide](#2026-06-16-bitrise-cicd-integration-guide)
3.  03[Test from specific countries using geo-location routing](#2026-06-16-geo-location-routing-device-presets)
4.  04[MCP tools now describe return shapes and next steps](#2026-06-16-mcp-tools-describe-return-shapes)
5.  05[PR review bot posts new GitHub comments for status updates](#2026-06-16-pr-review-bot-new-comments-for-status)

1.  Highlight
    
    Featured this release
    
    ## Post-run AI analysis and automatic reruns
    
    After each run completes, an AI agent classifies failures, re-runs flaky tests, and shows a full timeline in a new Analysis tab.
    
    When a run finishes with failures, QA.tech classifies each failing test as a real failure or a transient/platform flake and re-runs candidates automatically. Set the budget under Project Settings → General → "Automatic reruns" (Off, or 1–3 attempts per test per run). The "Analysis" tab on the run results page shows a chronological timeline of per-test classifications with reasoning, which tests were re-run, and settled outcomes. When the agent has a specific recommendation – like splitting a test that keeps hitting the step limit – it shows a "Fix in chat" button that opens the assistant prefilled with context.
    
    [\# Direct link](#2026-06-16-post-run-ai-analysis-and-automatic-reruns)
    
2.  Update 02 of 05
    
    ## Bitrise CI/CD integration guide
    
    New docs page for integrating QA.tech into a Bitrise pipeline for APK, IPA, and web app builds.
    
    Covers Android APK and iOS IPA upload-and-run flows, a plain HTTP trigger for web apps, and a polling recipe for using QA.tech as a release gate before a store submission. Linked from the CI/CD integration overview on docs.qa.tech.
    
    [\# Direct link](#2026-06-16-bitrise-cicd-integration-guide)
    
3.  Update 03 of 05
    
    ## Test from specific countries using geo-location routing
    
    Device presets now accept a region – US, UK, or Germany – and route the test browser through a residential proxy in that country.
    
    Select a region on any device preset to run the test through a residential/ISP proxy in that country. Locale and timezone follow the region automatically, so you get a full market simulation without configuring them separately.
    
    [\# Direct link](#2026-06-16-geo-location-routing-device-presets)
    
4.  Update 04 of 05
    
    ## MCP tools now describe return shapes and next steps
    
    Every create\_\* and start\_\* MCP tool now documents what it returns and which tool to call next.
    
    Each tool's description ends with a `Returns: { ... }` line matching the actual response shape and, for async operations, a `Next:` hint pointing at the right polling tool – for example, `start_run` → `get_run`. AI coding agents can chain calls without a discovery round-trip.
    
    [\# Direct link](#2026-06-16-mcp-tools-describe-return-shapes)
    
5.  Update 05 of 05
    
    ## PR review bot posts new GitHub comments for status updates
    
    QA.tech now posts a new comment on a pull request for each status update, instead of editing the previous one.
    
    GitHub notifies reviewers on new comments but not on edits – status updates now show up in the notification feed.
    
    [\# Direct link](#2026-06-16-pr-review-bot-new-comments-for-status)
    

## 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)
-   [PR Testing](https://qa.tech/product/pr-testing)
-   [MCP](https://qa.tech/product/mcp)
-   [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/)

© 2025 QA.tech. All rights reserved
