Test accounts
Store test accounts and use them in login steps.
Test accounts let the agent sign in during a test. They belong to the project and are available to all its environments and mobile builds. They are not the same as Operio organization accounts.
Add a test account
Open Settings → Project → Test Accounts, click Add Test Account, and choose a login method:
| Login method | What to provide |
|---|---|
| Password | Username or email and password. |
| Google email and password for a Sign in with Google flow. | |
| Phone & OTP | Test phone number with country code and a fixed verification code. |
| Custom | Instructions for a multi-step login, staging gate, or passcode flow. |
Give it a unique label, such as QA Admin. Add a description if the agent needs context about when to use that account, then save.
Use it in a test
Add a Login step and select the test account. Alternatively, type @ in an Action or Verify step and select its label.
The agent uses the stored account or follows the custom instructions. For example, a custom flow could say: “Open /internal/login, enter the staging passcode, then sign in with the demo account shown on the page.”
Phone login
Configure the number in your app or SMS provider as a test account that always accepts the same code. Store that number and code in a Phone & OTP test account.
Operio submits the stored code; it cannot receive a real SMS. A number that requires a newly generated SMS code will not work with this login method.
Update stored values
Open a test account to edit its label, description, account details, or custom instructions. Renaming preserves existing step references. Leave the password blank to keep its current value.
Secrets on a test account are encrypted at rest and decrypted server-side for the agent at run time. Saved passwords are not shown again in the UI.