Release notes··2 updates

    More reliable login automation

    2 updates shipped on May 7, 2026.

    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

    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

    Ready to end the QA bottleneck?

    See how QA.tech agents test your product in a 30-minute demo – and leave with a plan to reclaim those hours.

    Get a demo