# Smarter error classification and Coverage polish

> 2 updates: Coverage page polish, Smarter HTTP error classification

Source: https://qa.tech/changelog/2026-04-27

---
2 updates shipped on April 27, 2026.

In this release

1.  01[Coverage page polish](#2026-04-27-coverage-page-polish)
2.  02[Smarter HTTP error classification](#2026-04-27-smarter-http-error-classification)

1.  Update 01 of 02
    
    ## Coverage page polish
    
    Smaller fixes from the first month of Coverage being broadly available.
    
    A handful of changes off the back of customer feedback after the Coverage GA in April:
    
    -   "Top Gaps" CTA renamed to "Fix in chat" to make it obvious where the action goes.
    -   Tightened spacing throughout the Coverage page.
    -   Fixed a bug where the coverage progress bar was invisible at very low coverage values.
    
    [\# Direct link](#2026-04-27-coverage-page-polish)
    
2.  Update 02 of 02
    
    ## Smarter HTTP error classification
    
    A 4xx in the network log no longer fails an otherwise-passing test.
    
    When the agent saw a 4xx or 5xx response in the network log, it sometimes called the run a failure even when the user-visible step had clearly succeeded – common with API tests, with UI tests that pass through a 404 page on their unhappy path, and with apps that intentionally probe failure responses. The Assessment Agent now decides whether a transport-layer error is actually a real failure based on the test goal and what the user actually saw, instead of failing on the first non-200 in the log.
    
    [\# Direct link](#2026-04-27-smarter-http-error-classification)
    

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