A starting point: adapt these to your app. This page lists 13 test cases for signing up and verifying an email address, 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#
Creating an account with valid details and verifying the email, then the usual refusals: an email that already has an account, an address in the wrong format, a password that does not match its confirmation. Boundary cases check a password exactly at your minimum length and one character short of it, and an email typed with capitals and spaces. For verification, they check an expired link, a link used twice, resending the email, and what an unverified account may and may not do. A required terms box left unticked is covered too.
Why these matter#
Signup is where every new user meets your product, and a confusing error there loses them before they start. Verification is easy to get subtly wrong: links that never expire, links that work twice, or accounts that can do everything without ever confirming the address. 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 signup 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.