# Richer PR comments and a new test-cases API

> 2 updates: Create test cases via the public API, Failure reasons in PR review comments

Source: https://qa.tech/changelog/2026-01-09

---
2 updates shipped on January 9, 2026.

In this release

1.  01[Create test cases via the public API](#2026-01-09-create-test-cases-via-api)
2.  02[Failure reasons in PR review comments](#2026-01-09-failure-reasons-pr-comments)

1.  Update 01 of 02
    
    ## Create test cases via the public API
    
    A new \`/v1/test-cases\` endpoint creates tests programmatically.
    
    A new `POST /v1/test-cases` endpoint on the public API lets external systems create test cases with goals, expected results, and metadata. Useful for CI pipelines that want to register a test as part of a feature ticket, and for coding agents that want to author tests before implementing them.
    
    [\# Direct link](#2026-01-09-create-test-cases-via-api)
    
2.  Update 02 of 02
    
    ## Failure reasons in PR review comments
    
    The bot's PR comment now shows why each failed test failed, inline.
    
    When the PR review bot posts a comment with a results table, each failed row now includes a one-line failure reason directly in the table, so reviewers don't have to click through to QA.tech to see what went wrong. The full run is still one click away, but the most important context is now in the PR.
    
    [\# Direct link](#2026-01-09-failure-reasons-pr-comments)
    

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