TestFinch

Test cases for signup and verification

A starting set of signup and email verification checks, as a spreadsheet, CSV or Markdown.

A starting point: adapt these to your app. These cases cover creating an account with an email and password, and verifying the email. They are generic, not full coverage of your app: remove what does not apply and add what is special about yours.

Download .xlsxDownload .csvDownload .md

13 cases, with a How to use tab in the .xlsx

Signup and verification: 13 cases
IDTitleTypeStepsExpected result
SIG-01Create an account with valid detailsPositive
  1. Open the signup page
  2. Enter a new email and a valid password
  3. Select Create account
The account is created, and a page says a verification email was sent.
SIG-02The verification link verifies the emailPositive
  1. Open the verification email
  2. Select the link
A page says the email is verified, and the account can use everything that needs it.
SIG-03An email that already has an accountNegative
  1. Open the signup page
  2. Enter an email that already has an account, and a valid password
  3. Select Create account
A message says the email is in use and offers sign in or a password reset.
SIG-04An email in the wrong formatNegative
  1. Enter 'name@' as the email
  2. Select Create account
The email field says the address is not valid, and nothing is sent.
SIG-05A password one character short of the minimumBoundary
  1. Enter a password one character shorter than your app's minimum
  2. Select Create account
The password field says how long a password must be.
SIG-06A password exactly at the minimumBoundary
  1. Enter a password exactly as long as your app's minimum
  2. Select Create account
The account is created.
SIG-07The confirmation does not matchNegative
  1. Enter a password, and a different one to confirm it, if your form asks twice
  2. Select Create account
A message says the passwords do not match.
SIG-08An expired verification linkNegative
  1. Wait until the verification link expires, or use an old one
  2. Select the link
A page says the link has expired and offers to send a new one.
SIG-09A verification link used twiceNegative
  1. Verify the email with its link
  2. Select the same link again
A page says the email is already verified, with no error.
SIG-10Resend the verification emailPositive
  1. Sign up
  2. Select Resend email
A new email arrives, and the newest link works.
SIG-11An unverified account is limitedNegative
  1. Sign up but do not verify
  2. Try an action that needs a verified email
A message asks to verify the email first, with a resend option.
SIG-12Capitals and spaces in the emailBoundary
  1. Sign up with ' New.User@Example.com '
  2. Sign in later with 'new.user@example.com'
Both refer to the same account, if your app treats emails as case-insensitive.
SIG-13Required agreement not tickedNegative
  1. Fill in the form but leave the terms box unticked, if there is one
  2. Select Create account
The form says the terms must be accepted, and no account is created.

FlowQA's agent explores your site, writes the tests and runs them after every deploy, so you stop running them by hand. Free to start.

Try FlowQA free

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#

  1. 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).
  2. 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.
  3. 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.
  4. 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.