Accounts and access

Add whatever Quail needs to get past the front door and use your site the way your customers do: a login for each kind of person, a password if the whole site is locked, a browser pop-up login, or a special code your developers gave you. Up to 5 items per project.

• A login: a username and password for someone who signs in on a login page. Add one per kind of person (an admin, a customer)
• A password for the whole site: for test and staging sites that ask for one password before showing anything. The username is optional
• A browser pop-up login: the small sign-in box your browser shows by itself, before the page loads
• A special code: a header or cookie your developers gave you, sent with every request
• Check: tries the item on your site and tells you if it works. Some sign-in pages are driven by scripts and can only be confirmed by a real run, so the answer can be Couldn't tell yet
• Explore re-checks every item on each run and marks any that stop working, so a changed password shows up here instead of quietly weakening your tests
• Stored encrypted and never shown again. Use dedicated test accounts, not a real customer's