# More reliable login automation

> 2 updates: Agent handles MFA logins more reliably, Faster, more reliable captcha handling

Source: https://qa.tech/changelog/2026-05-07

---
2 updates shipped on May 7, 2026.

In this release

1.  01[Agent handles MFA logins more reliably](#2026-05-07-agent-handles-mfa-logins-more-reliably)
2.  02[Faster, more reliable captcha handling](#2026-05-07-faster-reliable-captcha-handling)

1.  Update 01 of 02
    
    ## Agent handles MFA logins more reliably
    
    The AI agent's ability to test apps with MFA logins is now more stable.
    
    When the QA.tech agent tests an application with MFA enabled, it has to read a one-time code from the email or authenticator inbox and submit it before the code expires. Tests were occasionally failing because the captcha resolver would time out between reading the OTP and filling in the form, expiring the code mid-submission.
    
    We tightened the timing on that path. If you have tests against an MFA-protected login flow that were occasionally flaking, they should be stable now.
    
    To be clear: this is about the agent testing your app, not about how you log in to QA.tech. Your own QA.tech login flow is unaffected.
    
    [\# Direct link](#2026-05-07-agent-handles-mfa-logins-more-reliably)
    
2.  Update 02 of 02
    
    ## Faster, more reliable captcha handling
    
    Captcha-protected pages resolve faster and fail more clearly when they can't.
    
    The captcha resolver got two changes worth mentioning. It's faster on the happy path, which matters because login flows often sit behind a captcha and that wait was previously the longest single step in many tests. It also handles invalid captchas more cleanly: instead of retrying silently until it times out, it surfaces the failure so the test fails fast with a useful reason.
    
    [\# Direct link](#2026-05-07-faster-reliable-captcha-handling)
    

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