# MCP tools for failing tests, PR list redesign, and check-run controls

> 5 updates: Investigate failing tests through the API and MCP tools, Automatic reruns now reach large failing runs, Inconclusive PR reviews now resolve as…

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

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

In this release

1.  01[Investigate failing tests through the API and MCP tools](#2026-06-23-investigate-failing-tests-via-api-mcp)Highlight
2.  02[Automatic reruns now reach large failing runs](#2026-06-23-automatic-reruns-reach-large-runs)
3.  03[Inconclusive PR reviews now resolve as a passing GitHub check](#2026-06-23-inconclusive-pr-reviews-pass-github-check)
4.  04[Pull Requests page redesigned as a table](#2026-06-23-pull-requests-page-table-redesign)
5.  05[Skip the GitHub check run for PR reviews](#2026-06-23-skip-github-check-for-pr-reviews)

1.  Highlight
    
    Featured this release
    
    ## Investigate failing tests through the API and MCP tools
    
    Three new tools let AI coding agents fully investigate any failing test – detail, step-by-step trace, and pass/fail history – without touching the dashboard.
    
    `get_run_test_case` returns per-test detail for any result ID from a `qa.tech/results/test/` URL: goal, success criteria, evaluator reasoning, error classification, durations, and a durable deep link. `get_run_test_case_trace` gives a paginated step-by-step agent trace – reasoning, tool calls, observations, and screenshots – so large test suites don't overflow context. `get_test_case_history` shows the recent pass/fail trend and durations across runs, making it straightforward to tell a flake from a regression.
    
    All three are available as [MCP tools](https://qa.tech/product/mcp) and via the REST API under `/v1/run-test-case`. Pasting a `/results/test/` URL directly into the chat assistant now resolves to the correct run and test, with a cross-project hint shown when the URL points to a project other than the one currently in scope.
    
    [\# Direct link](#2026-06-23-investigate-failing-tests-via-api-mcp)
    
2.  Update 02 of 05
    
    ## Automatic reruns now reach large failing runs
    
    Flaky-test analysis and automatic reruns now apply to runs of any size.
    
    Every failing run – no matter how many tests failed – now flows through the same batched flaky-test classifier that smaller runs use. Per-test rerun budgets and pass limits still bound how many reruns fire, so the analysis stays bounded on very large suites too.
    
    [\# Direct link](#2026-06-23-automatic-reruns-reach-large-runs)
    
3.  Update 03 of 05
    
    ## Inconclusive PR reviews now resolve as a passing GitHub check
    
    When QA.tech can't complete a PR review, the GitHub Check Run now shows green instead of grey.
    
    If QA.tech reviewed your PR but couldn't reach a verdict – because the diff was outside the configured scope or the PR couldn't be assessed – the resulting GitHub Check Run previously appeared as "skipped" (grey dash). It now resolves as "success" (green tick), so branches protected by required-status checks or auto-merge rules continue unblocked. The "Review inconclusive" indicator on the QA.tech dashboard still reflects the actual verdict; only the GitHub merge gate changes.
    
    [\# Direct link](#2026-06-23-inconclusive-pr-reviews-pass-github-check)
    
4.  Update 04 of 05
    
    ## Pull Requests page redesigned as a table
    
    The Pull Requests page now displays as a clean table and defaults to showing open PRs when any exist.
    
    The PR list has been replaced with a table layout that matches the Results page – white background, aligned headers, and compact review-count badges. When you open Pull Requests for a project, it now defaults to "Open" if there are open PRs, so you land on what's active rather than the full history. If there are no open PRs, it falls back to "All". The repository column and filter picker are removed; the search box still finds PRs by repo name.
    
    [\# Direct link](#2026-06-23-pull-requests-page-table-redesign)
    
5.  Update 05 of 05
    
    ## Skip the GitHub check run for PR reviews
    
    A new per-repository toggle lets you run QA.tech PR reviews without posting a GitHub check run.
    
    Under Settings → Integrations → GitHub App, each repository's "Pull Request Testing" section now has a "Register a commit check" switch, on by default. Turn it off and QA.tech still runs the [review](https://qa.tech/product/pr-testing), posts its sticky comment, and records the result in the dashboard – but it won't create or update the `QA.tech / PR Review` check in GitHub. Useful when you want automated reviews without affecting branch protection or merge-gating rules. The "Block merges when a review fails" option is hidden when the toggle is off, since that workflow requires a check.
    
    [\# Direct link](#2026-06-23-skip-github-check-for-pr-reviews)
    

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