Sign-ins
Save an account once per environment so test cases can start already signed in.
A sign-in is an account you save once in an environment, like admin or free-user. A test case that starts signed in skips the login screen: the run signs in during setup, checks it worked, and only then starts step 1.
Use sign-ins for everything except testing the sign-in page itself. For that, leave the test case signed out and write the login steps.
Add a sign-in
- Open Environments, pick the environment, and go to its Settings tab.
- Under Sign-ins, choose Add a sign-in.
- Give it a role: a short name such as
adminorfree-user. Test cases pick sign-ins by role, so the same role can point at a different account in each environment. - Choose how the account signs in (see below).
- Tell Autonomy how to know it worked:
- Text you only see when signed in, such as “Sign out” or “My account”. Required.
- Text that shows it's this account, such as the name in the account menu. Optional.
- Choose Save sign-in.
The sign-in shows Not checked yet until the first run uses it.
Username & password
Enter the username and password, or pick environment values you already have. New details are saved as environment values: the username as SIGNIN_<ROLE>_USERNAME and the password as a secret, SIGNIN_<ROLE>_PASSWORD. Secrets can't be viewed again after saving, and only the test run receives them.
If your login needs extra steps, choose Use one of your routines instead and pick a routine that signs in.
Works on web, iOS and Android.
Save a login from your browser
For accounts you can't script, such as ones behind a company login, sign in yourself once and let the Autonomy browser extension save that login.
- Install the Autonomy extension for Chrome.
- In the dialog, name the account under Which account is this? and save. The sign-in shows Waiting for your browser.
- Open your app in a new tab and sign in as usual.
- Click the Autonomy icon in the toolbar and choose Save login on that sign-in.
- Review What we keep, the sites and number of cookies and values the extension will save, then save.
Chrome asks for permission to read that one site before anything is read. The login is stored as a secret. The extension keeps nothing on your computer. Only you can renew a login you saved.
Web only.
Start a test case signed in
In the test case's preconditions, set Start signed in as to the role. The run uses that role's account in whichever environment it runs in.
If another environment doesn't have that role, the test case warns you before you run it there.
Status
| Status | Meaning |
|---|---|
| Not checked yet | Saved; no run has used it yet. |
| Working | The last sign-in worked. |
| Needs you | Sign-in failed twice in a row. Check the password, or renew the saved login. |
| Fix check | The “signed in” text was also visible while signed out, so Autonomy can't tell whether sign-in worked. Pick text that only appears after signing in. |
| Waiting for your browser | Created, but no login has been saved from the extension yet. |
When a run couldn't start
If the sign-in fails during setup, the run stops before step 1 and shows Couldn't start. These runs aren't failures of your app, so they don't count toward pass rate. The run page says which check failed.
One account is used by one run at a time, so parallel runs don't sign each other out.
Didn’t find it?