TestFinch

Test cases for login and logout

A starting set of login and logout checks, as a spreadsheet, CSV or Markdown.

A starting point: adapt these to your app. These cases cover signing in with an email and password, and signing out. 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

Login and logout: 13 cases
IDTitleTypeStepsExpected result
LOG-01Sign in with a registered email and its passwordPositive
  1. Open the sign in page
  2. Enter a registered email and its password
  3. Select Sign in
The signed-in home page opens and shows the account's name.
LOG-02A wrong password is refusedNegative
  1. Open the sign in page
  2. Enter a registered email and a wrong password
  3. Select Sign in
A message says the email or password is wrong, without saying which. The page stays on sign in.
LOG-03An unregistered email gets the same messageNegative
  1. Enter an email with no account and any password
  2. Select Sign in
The same message as for a wrong password shows, so nobody can learn which emails have accounts.
LOG-04Empty fields are refused before sendingNegative
  1. Leave the email and password empty
  2. Select Sign in
Each empty field is marked as required, and nothing is sent.
LOG-05The email's letter case does not matterBoundary
  1. Enter the registered email in capitals, with the right password
  2. Select Sign in
Sign in works, if your app treats emails as case-insensitive (most do).
LOG-06Spaces around the email are ignoredBoundary
  1. Enter the registered email with a space before and after it
  2. Enter the right password and select Sign in
Sign in works, because the spaces are trimmed.
LOG-07Repeated failures are slowed downNegative
  1. Enter a wrong password as many times as your app allows
  2. Try once more
After the limit, a message says to wait or reset the password, and further attempts are refused for a while.
LOG-08The password is hidden as it is typedPositive
  1. Type a password in the password field
  2. Select the show password control, if there is one
The characters show as dots, and the control reveals and hides them.
LOG-09Sign in returns to the page that was asked forPositive
  1. While signed out, open a link to a page that needs an account
  2. Sign in
The page that was asked for opens, not the home page.
LOG-10Keyboard only sign inPositive
  1. Use Tab to reach the email, the password and the button
  2. Press Enter in the password field
Focus moves in order with a visible outline, and Enter signs in.
LOG-11Sign out ends the sessionPositive
  1. While signed in, select Sign out
  2. Press the browser's back button
The sign in page shows, and the back button does not show the account's pages.
LOG-12A saved account link needs sign in after sign outNegative
  1. Sign out
  2. Open a bookmarked account page
The sign in page opens instead of the account page.
LOG-13A very long passwordBoundary
  1. Enter a password of 128 characters on the sign in form
  2. Select Sign in
It is accepted, or refused with a clear message. It is never cut short without telling the user.

FlowQA's agent explores your site and writes cases like this one as tests, keeping each only once it has passed twice and failed on a deliberately broken page. Free to start.

Try FlowQA free

The manual case

SMK-02 A registered user can sign in

  1. Open Sign in
  2. Enter a test account's email and password
  3. Select Sign in

Expected: the account page opens with the user's name.

The FlowQA test

account/sign-in

  1. navigate "/sign-in"
  2. fill "Email" with "mia@acme.example"
  3. fill "Password" with "••••••••"
  4. tap button "Sign in"
  5. assert url matches "/account"
  6. assert text "Mia Chen" is visible

An illustration with sample data.

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#

  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#

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.