# OpenAPI coverage, unattended exploratory reviews, and performance in test plans

> 6 updates: Import OpenAPI endpoints into the coverage map, Exploratory reviews plan probes and run unattended, Four PR review verdicts with named bugs,…

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

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

In this release

1.  01[Import OpenAPI endpoints into the coverage map](#2026-11-17-openapi-coverage-map)Highlight
2.  02[Exploratory reviews plan probes and run unattended](#2026-11-17-unattended-exploratory-reviews)Highlight
3.  03[Four PR review verdicts with named bugs](#2026-11-17-four-pr-review-verdicts)
4.  04[Show PR risk as a GitHub label](#2026-11-17-github-pr-risk-labels)
5.  05[Track performance on every test plan run](#2026-11-17-performance-test-plan-runs)
6.  06[Manage applications, environments and scenarios through API and MCP](#2026-11-17-project-management-api-mcp)

1.  Highlight
    
    Featured this release
    
    ## Import OpenAPI endpoints into the coverage map
    
    The coverage map imports API endpoints from OpenAPI and Swagger specs and connects them to calling pages.
    
    The Coverage page now imports endpoints from OpenAPI 3.x or Swagger 2 specifications found at common paths and refreshes them daily. Endpoints are clustered by tag, shown as diamonds or stars when tested, with dashed outlines for undocumented endpoints.
    
    Animated lines connect web pages to the endpoints they call. Selecting an endpoint shows where it was observed and which pages call it. API tests receive the endpoint list before execution, so the agent knows which endpoints are available.
    
    More on this: [API testing](https://qa.tech/product/api-testing), [API contract testing](https://qa.tech/use-cases/api-contract-testing) and [API regression testing](https://qa.tech/use-cases/api-regression-testing).
    
    [\# Direct link](#2026-11-17-openapi-coverage-map)
    
2.  Highlight
    
    Featured this release
    
    ## Exploratory reviews plan probes and run unattended
    
    Exploratory reviews plan their probes, execute parallel test batches and run unattended when started by an automation.
    
    Exploratory reviews use project knowledge and, when enabled, code access to plan probes for state changes, sorts and filters, edge-case inputs, failure paths, narrow screens, keyboard use and other users. They execute parallel batches of short draft tests, applying [agentic testing](https://qa.tech/) to the planned scope.
    
    With a time budget, new batches continue until about 80% of the budget is used. Each distinct confirmed bug gets a finding, without the previous 20-finding cap. Automation-started reviews take their scope from the kickoff message and run without stopping for questions.
    
    More on this: [exploratory testing](https://qa.tech/use-cases/exploratory-testing) and [automated exploratory testing](https://qa.tech/blog/automated-exploratory-testing).
    
    [\# Direct link](#2026-11-17-unattended-exploratory-reviews)
    
3.  Update 03 of 06
    
    ## Four PR review verdicts with named bugs
    
    PR reviews distinguish confirmed bugs, full verification, partial verification and changes that could not be verified.
    
    PR reviews now finish with Bugs Found, Fully Verified, Partially Verified or Can't Verify. Bugs Found means a test confirmed a functional bug and the GitHub check fails. Fully Verified and Partially Verified pass the check; Can't Verify is non-blocking.
    
    Any confirmed bug on a page reached by the tests counts as Bugs Found, including a pre-existing bug, and can block a merge under branch protection. Improvement suggestions do not affect the status. The summary names each confirmed bug, describes the three worst individually and lists any others together.
    
    More on this: [PR testing](https://qa.tech/product/pr-testing) and [the pull request checklist](https://qa.tech/blog/pull-request-checklist).
    
    [\# Direct link](#2026-11-17-four-pr-review-verdicts)
    
4.  Update 04 of 06
    
    ## Show PR risk as a GitHub label
    
    A PR review rule can label GitHub pull requests with their assessed risk level.
    
    Add Risk Label on the PR from the rule library as a PR review rule. QA.tech applies `qa:risk:low`, `qa:risk:medium`, `qa:risk:high` or `qa:risk:unknown` as soon as risk assessment finishes, before test creation.
    
    A later commit that changes the risk level replaces the old label. QA.tech only adds or removes labels beginning with `qa:` and creates missing labels when needed. This rule currently works on GitHub.
    
    More on this: [risk-based PR testing](https://qa.tech/blog/risk-based-testing-pull-requests) and [PR testing](https://qa.tech/product/pr-testing).
    
    [\# Direct link](#2026-11-17-github-pr-risk-labels)
    
5.  Update 05 of 06
    
    ## Track performance on every test plan run
    
    Test plan settings can enable performance recording for scheduled, CI, API and manual runs.
    
    Open a test plan → Settings and turn on Record performance metrics in the Performance Metrics section. Every run of that plan records performance, including scheduled, CI and API runs. Chat can also enable or disable recording when creating or editing a plan.
    
    Run reviews with performance data include a Performance section identifying vitals outside Google’s good range and the affected pages. It lists up to five of the slowest tests with a short measurement note.
    
    More on this: [test plans](https://docs.qa.tech/core-concepts/test-plans) and [web testing](https://qa.tech/product/web-testing).
    
    [\# Direct link](#2026-11-17-performance-test-plan-runs)
    
6.  Update 06 of 06
    
    ## Manage applications, environments and scenarios through API and MCP
    
    New API and MCP operations manage application settings, environment access and test scenario folders.
    
    The API can update application names, colors and session state lifetime. Environment operations can delete environments or create and update custom header rules and HTTP Basic Auth credentials, matching Settings → Applications & Envs. Passwords are write-only. Scenario operations list, create, rename, move and delete test scenario folders.
    
    MCP now uses one `manage_*` write tool per entity, such as `manage_rules`, `manage_test_plans` and `manage_environments`, with `operation: create | update | delete`. The old per-operation tools remain compatible but are hidden from the tool list.
    
    More on this: [MCP for coding agents](https://qa.tech/product/mcp), [API reference](https://docs.qa.tech/api-reference/introduction) and [applications and environments](https://docs.qa.tech/core-concepts/applications-and-environments).
    
    [\# Direct link](#2026-11-17-project-management-api-mcp)
    

## 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
