Test services that require login

echo does not save passwords. A person logs in on the login browser screen, and the login state, such as cookies, is saved on this PC. As long as it remains valid on the service side, later runs use that state. When the browser for a run or for "Create with AI" closes, cookies and other state that changed in the meantime are written back to the saved state (so even if the service changes the session's contents, the next browser picks up where it left off; nothing is written back while the login screen is showing).

Log in before a test

If a named account's login state hasn't been saved, you are asked to log in when the test starts. You can also log in beforehand from Accounts in the bottom bar.

1. On the login screen shown in the Browser in echo's main area, enter your email address, password, two-step verification, and so on.
2. When the post-login screen appears, choose I'm Logged In.
3. The login state is saved and the test starts.

For services that use passkeys, register and use a passkey for echo in echo's browser. Passkeys from Touch ID / iCloud Keychain on Mac or Windows Hello can't be used from echo's browser, so register a new passkey from echo's browser, for example on the service's settings screen. Each registration and login is confirmed with Touch ID (or your Mac password). Registered passkeys are encrypted and saved on this PC per account, and are not synced with other PCs. You can view and delete them under Passkeys in the Page tab on the right.

You can also use passkeys on your phone. When you use a passkey on a site that has no echo passkey, a QR code appears in the browser frame; scan it with your phone's camera and confirm on your phone. Turn on Bluetooth on both your PC and phone and scan nearby (the first time, echo asks for permission to use Bluetooth). On iPhone, you scan the QR code every time. When a QR code appears during passkey registration, you can also choose Create on This PC to register it as an echo passkey.

If there is a step you can't complete in echo's browser, you can open it in your usual browser with Open in Separate Window under ⋯ (logins there are not saved in echo).

When you run with the default account, or when a saved login has expired, you may be asked to log in after the test stops at the login screen. After you log in, the test reruns from the beginning.

Skip login

To continue without logging in, for example to check the login screen itself, choose Skip Login. You won't be asked to log in to the same account again during that run. Tests that require login are not run and are skipped.

Manage login states

From Accounts in the bottom bar, you can log in, log in again, or discard a saved login state. To test with multiple roles, see Using accounts.

Login states are saved in the app's settings area, not in the project folder. Screens and input during login are not kept in recordings or run logs. For details on where data is stored, see Data storage location.