Skip to main content
Store login data in Configs and attach the right config to each test. The agent uses those values when it hits a login form or needs a token. Prefer dedicated test accounts; config values are passed to the AI during runs. If your preferred method is not listed below, tell us and we will consider it for the roadmap.

​
Choose a method

Create configs under Project Settings → Configs, then add them on the test Settings tab. Field-level setup for each type lives on the Configs page. Environment-specific values use Config Environment Overrides.

​
Two-Factor Authentication (2FA)

For TOTP (Google Authenticator, Authy, and similar), create a Username + Password Credentials - with Two-Factor Authentication config and paste the full otpauth:// URI from the account’s QR code:
  1. In your app, open 2FA setup for the test user until the QR code appears. Do not scan it with a phone.
  2. Decode the QR (for example with scanqr.org) and copy the otpauth://totp/... URI.
  3. Save that URI on the config in Project Settings → Configs. Field names are on Configs.
During login the agent generates a fresh code from the URI. You do not need a step that says “enter the 2FA code.”

​
What we don’t support

  • CAPTCHA challenges — Most CAPTCHA types (reCAPTCHA, hCAPTCHA, and similar) are not supported.
  • BankID without a stub — Production BankID is not automated end to end; use a staging stub or the BankID live-stream flow.
Avoid CAPTCHA on staging: Allowlist QA.tech IP addresses so tests are not blocked. Find them in Settings → Network and see IP Access Control.

​
Parallel runs and rate limits

When many tests log in at once, identity providers can rate-limit or invalidate sessions. Configure provider limits before scaling parallel plans. See Authentication Rate Limits.