What an app holds
Every app has its main test login — the one on the “Test login” card — and up to ten named test accounts next to it: “admin”, “free user”, “team member”, whatever your product calls its kinds of user. Each has its own email and password, kept exactly like the main one: encrypted, never shown back, typed only into your app’s own pages.
Adding them
- In the dashboard — your app → “More test accounts”. Type a name, an email and a password on the empty row and press Save settings. Rename an account or change its email in place; leave its password empty to keep the current one; tick Remove to delete it.
- From your coding agent —
create_appandupdate_apptaketest_accounts: [{label, email, password}], andremove_test_accountsdeletes by name.list_appsshows every account’s name and email, never a password. See Connect your coding agent.
Saying which account a scenario runs as
Name the account at the start of the scenario, in “What worries you most?”:
As admin: refunds go through and show up in the order history.As free user: the Export button offers an upgrade instead of exporting.Checkout must never break.— names no account, so it runs as the main test login.
Every check of the app — the ones you start and the daily ones — has all of its accounts and signs in as the one each scenario names. A scenario that names an account the app does not have is reported as not checked rather than guessed at.
When one account’s password stops working
The same rule as for the main login, per account: that account is tried once, nothing behind it is called broken, and the result names which account’s sign-in details need replacing. The other accounts keep being checked in the same run.
good to know
A single check from the home pagecarries one login, the one you type under “Add login & notes”. A role on its own address, such as admin.example.com, is its own app with its own accounts. A Chrome extension signs in with its one test login.