A starting point: adapt these to your app. This page lists 13 test cases for signing in and signing out, each with numbered steps and an expected result, and gives them to you as an Excel workbook, a CSV file or Markdown.
How to use it#
- Read the cases on this page. Each is marked Positive (the normal path), Negative (wrong input or a refused action) or Boundary (at or just past a limit).
- Select Download .xlsx for a workbook with a How to use tab and a tab of the cases, with Status set to Not run and blank rows for your own.
- Or select Download .csv to import the cases into another tool or a shared sheet, or Download .md to paste them into a wiki, a pull request or a test plan.
- Remove what does not apply to your app, change the steps to match your screens, and add what is special about yours.
What the cases cover#
Signing in with the right email and password, and the messages for a wrong password, an unknown email and empty fields. The cases check that both failures get the same message, so nobody can learn which emails have accounts. They check limits too: letter case and spaces around the email, a very long password, and what happens after repeated failures. For signing out, they check that the session ends, that the back button does not show account pages, and that a saved link asks for sign in again. Keyboard-only sign in and returning to the page that was asked for are covered too.
Why these matter#
Sign in is the door to everything else, so a fault there stops every user at once. It is also where small mistakes leak information: an error that says "no account with this email" tells anyone which addresses are registered. Writing them down once, with expected results someone else can check, turns a quick look before a release into a repeatable check.
What they do not cover#
These are generic cases. They do not know your app's rules, its other ways in, or its edge cases, so they are not full coverage. Read each expected result against how your app is meant to behave: some apps deliberately differ, and that is a decision to confirm, not a failure.
Questions#
Do these cover every login case?#
No. They are a starting point; adapt them to your app.
Can I edit them?#
Yes. Download the spreadsheet or the Markdown and change anything.
Is this free?#
Yes, with no account. Use the cases in your own plans and tools.
Can these run automatically?#
Not from this page; they are written for a person to follow. Each one is specific enough to automate later with the test tool your team uses.