# Exploratory reports, API coverage maps, and mobile builds from CI

> 6 updates: Exploratory runs finish with an app report, API endpoints on the coverage map, Edit coverage data through chat, Promote a mobile environment…

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

---
6 updates shipped on November 6, 2026.

In this release

1.  01[Exploratory runs finish with an app report](#2026-11-06-exploratory-run-reports)Highlight
2.  02[API endpoints on the coverage map](#2026-11-06-api-endpoints-coverage-map)
3.  03[Edit coverage data through chat](#2026-11-06-edit-coverage-through-chat)
4.  04[Promote a mobile environment build from CI](#2026-11-06-mobile-default-build-from-ci)
5.  05[PR review rounds in the chat panel](#2026-11-06-pr-review-rounds-in-chat)
6.  06[Repository onboarding identifies missing test setup](#2026-11-06-repository-test-setup-analysis)

1.  Highlight
    
    Featured this release
    
    ## Exploratory runs finish with an app report
    
    Exploratory runs finish with a structured report in the side panel: an overall verdict, prioritized findings, explored areas and next steps.
    
    Exploratory runs finish with a structured report in the side panel: an overall verdict, prioritized findings, explored areas and next steps. Findings link to supporting test runs, while flaky or outdated tests appear separately under Test upkeep. Start the same workflow with /explore.
    
    More on this: [exploratory testing](https://qa.tech/use-cases/exploratory-testing) and [web testing](https://qa.tech/product/web-testing).
    
    [\# Direct link](#2026-11-06-exploratory-run-reports)
    
2.  Update 02 of 06
    
    ## API endpoints on the coverage map
    
    API applications show frequently observed endpoints as nodes on the Coverage page, grouped in their own area.
    
    API applications show frequently observed endpoints as nodes on the Coverage page, grouped in their own area. An endpoint is marked covered when a test touches it.
    
    More on this: [API testing](https://qa.tech/product/api-testing) and [api regression testing](https://qa.tech/use-cases/api-regression-testing).
    
    [\# Direct link](#2026-11-06-api-endpoints-coverage-map)
    
3.  Update 03 of 06
    
    ## Edit coverage data through chat
    
    Ask chat to update outdated pages, descriptions, elements or features in your coverage map.
    
    Ask chat to update outdated pages, descriptions, elements or features in your coverage map. It previews changes and applies them only after confirmation. Later crawls preserve feature names and descriptions you have edited.
    
    More on this: [product](https://qa.tech/product) and [exploratory testing](https://qa.tech/use-cases/exploratory-testing).
    
    [\# Direct link](#2026-11-06-edit-coverage-through-chat)
    
4.  Update 04 of 06
    
    ## Promote a mobile environment build from CI
    
    Use the API or set\_environment\_application\_build MCP tool to set the mobile build an environment uses by default.
    
    Use the API or set\_environment\_application\_build MCP tool to set the mobile build an environment uses by default. The environment list also returns the current default build, so CI can keep scheduled tests aligned with the latest merged application.
    
    More on this: [mobile testing](https://qa.tech/product/mobile-testing) and [MCP](https://qa.tech/product/mcp).
    
    [\# Direct link](#2026-11-06-mobile-default-build-from-ci)
    
5.  Update 05 of 06
    
    ## PR review rounds in the chat panel
    
    Opening a pull request takes you to its review chat.
    
    Opening a pull request takes you to its review chat. A Reviews tab lists rounds newest first and shows live progress for the current round, alongside Conversation, Files changed and Commits. Pull requests without a review open a conversation ready to start one.
    
    More on this: [PR testing](https://qa.tech/product/pr-testing) and [product](https://qa.tech/product).
    
    [\# Direct link](#2026-11-06-pr-review-rounds-in-chat)
    
6.  Update 06 of 06
    
    ## Repository onboarding identifies missing test setup
    
    Connecting a repository now checks the code for test users, roles, plans, feature flags, integrations, onboarding gates and seed data.
    
    Connecting a repository now checks the code for test users, roles, plans, feature flags, integrations, onboarding gates and seed data. Onboarding compares those requirements with your project configuration and records prioritized gaps in its report and todos.
    
    More on this: [integrations](https://qa.tech/product/integrations) and [PR testing](https://qa.tech/product/pr-testing).
    
    [\# Direct link](#2026-11-06-repository-test-setup-analysis)
    

## Your team moves fast. Can your testing keep up?

Our QA agents test your product autonomously, so moving fast never means shipping broken. Start free or get a 30-minute demo.

[Get started for free](https://app.qa.tech/auth/sign-up)[Book 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)](https://trust.qa.tech/)

### Product

-   [API Testing](https://qa.tech/product/api-testing)
-   [MCP](https://qa.tech/product/mcp)
-   [Mobile Testing](https://qa.tech/product/mobile-testing)
-   [PR Testing](https://qa.tech/product/pr-testing)
-   [Voice Testing](https://qa.tech/product/voice-testing)
-   [Web Testing](https://qa.tech/product/web-testing)

-   [AI QA testing guide](https://qa.tech/ai-qa-testing)
-   [Changelog](https://qa.tech/changelog)
-   [Integrations](https://qa.tech/product/integrations)
-   [Platform overview](https://qa.tech/product)
-   [Use cases](https://qa.tech/use-cases)

### Compare

-   [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress)
-   [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl)
-   [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright)
-   [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf)

-   [B2B SaaS testing](https://qa.tech/saas)
-   [Ecommerce testing](https://qa.tech/industries/ecommerce)
-   [For CTOs](https://qa.tech/solutions/ctos)
-   [For QA teams](https://qa.tech/solutions/qa-testers)

### 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)
-   [Partner Program](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)
-   [Trust Center: 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
