TemplateExcel · 3 sheets

Test case template

A ready Excel sheet for writing and running manual test cases, with 8 filled examples for a login page and a summary that counts results for you.

Download Excel29 KB
Preview of the Test case template Excel file

How to start

  1. Go to the Test cases sheet.
  2. Fill the light yellow cells at the top: project, module, build, environment, your name and date.
  3. Read the 8 example rows for a Login page. They show the format. Delete them or write over them.
  4. Write one test case per row. When you run the test, fill Actual result, Status and Bug ID.
  5. Open the Summary sheet to see your counts and pass rate. It updates by itself.

Details at the top of the sheet

Fill these light yellow cells first. The values below are the example.

ProjectDemo Shop web app
Module / FeatureLogin page
Build / versionv2.3.1
EnvironmentQA server, Chrome on Windows 11
Tested byYour name
Date21-Oct-2026

The 8 example test cases rows 7 to 14 of the Test cases sheet

TC-LOGIN-01PassHigh priority

Login with a valid email and password

Preconditions
User account exists and is active.
User is logged out.
Test data
Email: testuser1@example.com
Password: Test@1234
Steps
  1. Open the login page.
  2. Enter the registered email in the Email field.
  3. Enter the correct password in the Password field.
  4. Click “Login”.
Expected result
User goes to the Home page.
User’s name shows at the top right.
Actual result
User went to the Home page.
Name shows at the top right.

TC-LOGIN-02PassHigh priority

Login with a wrong password

Preconditions
User account exists and is active.
User is logged out.
Test data
Email: testuser1@example.com
Password: Wrong@999
Steps
  1. Open the login page.
  2. Enter the registered email.
  3. Enter a wrong password.
  4. Click “Login”.
Expected result
Error message shows: “Invalid email or password”.
User stays on the login page.
Password field is cleared.
Actual result
Same error message shown.
User stayed on the login page.
Password field cleared.

TC-LOGIN-03FailMedium priority

Login with empty Email and Password fields

Preconditions
User is on the login page.
Test data
Email: (leave blank)
Password: (leave blank)
Steps
  1. Open the login page.
  2. Leave the Email field empty.
  3. Leave the Password field empty.
  4. Click “Login”.
Expected result
Login does not happen.
“Email is required” shows under the Email field.
“Password is required” shows under the Password field.
Actual result
Page reloaded with no error message.
No message shown under either field.
Bug ID
BUG-101
Notes
Screenshot attached in BUG-101.

TC-LOGIN-04PassMedium priority

Login with an email that is not registered

Preconditions
The email below has no account in the app.
Test data
Email: nouser@example.com
Password: Test@1234
Steps
  1. Open the login page.
  2. Enter the unregistered email.
  3. Enter any password.
  4. Click “Login”.
Expected result
Error message shows: “Invalid email or password”.
The message does not say whether the email exists.
Actual result
Same error message shown.
Message does not reveal whether the email exists.

TC-LOGIN-05PassMedium priority

Password is hidden while typing

Preconditions
User is on the login page.
Test data
Password: Test@1234
Steps
  1. Open the login page.
  2. Type the password in the Password field.
  3. Look at the Password field.
  4. Click the eye icon next to the field.
  5. Click the eye icon again.
Expected result
Password shows as dots while typing.
After step 4 the password shows as plain text.
After step 5 it shows as dots again.
Actual result
Password shown as dots.
Eye icon showed and hid the text correctly.

TC-LOGIN-06BlockedHigh priority

Account locks after 5 wrong password tries

Preconditions
Account testuser2@example.com exists and is not locked.
Test data
Email: testuser2@example.com
Wrong password: Wrong@999
Correct password: Test@1234
Steps
  1. Open the login page.
  2. Enter the email and the wrong password.
  3. Click “Login”.
  4. Repeat steps 2 and 3 four more times (5 wrong tries in total).
  5. Enter the email and the correct password.
  6. Click “Login”.
Expected result
After the 5th wrong try, a message says the account is locked.
In step 6 the user still cannot log in while the account is locked.
Actual result
Could not test. Account lock setting is turned off on the QA server in this build.
Notes
Asked the dev team to turn on the lock setting. Retest in the next build.

TC-LOGIN-07PassMedium priority

“Forgot password?” link opens the reset page

Preconditions
User is logged out.
Test data
None
Steps
  1. Open the login page.
  2. Click the “Forgot password?” link.
Expected result
Forgot Password page opens.
Page has an Email field and a “Send reset link” button.
Actual result
Forgot Password page opened with the Email field and the button.

TC-LOGIN-08Not runHigh priority

User stays logged out after Logout and browser Back button

Preconditions
User account exists and is active.
Test data
Email: testuser1@example.com
Password: Test@1234
Steps
  1. Log in with the valid email and password.
  2. Open the My Account page.
  3. Click “Logout”.
  4. Click the browser Back button.
  5. Refresh the page.
Expected result
My Account page does not open.
User is sent to the login page.
No account details are visible.
Notes
Planned for the next test cycle.

What the colours mean

Light yellowFill these in. You will find them at the top of the Test cases sheet.
Dark headerColumn names. Please do not rename them, because the Summary depends on them.
White rowsYour test cases go here, one per row. Dropdowns are already set for Status and Priority.
Summary numbersThese are formulas. Please do not type over them.

What each column means

TC IDA short unique ID for the test case, like TC-LOGIN-01.
ModuleThe part of the app you are testing, like Login, Cart or Payment.
ScenarioOne line that says what you are checking.
PreconditionsWhat must already be true before you start, like “User is logged out”.
Test dataThe exact values you will type or use. Write the real values, not “valid email”.
StepsNumbered actions, one per line. For a new line inside a cell press Alt+Enter (Mac: Control+Option+Return).
Expected resultWhat should happen if the app works as per the requirement.
Actual resultWhat really happened when you ran the test.
StatusThe result of the run. Pick it from the dropdown (see below).
PriorityHow important the case is. Pick High, Medium or Low.
Bug IDThe bug number from your bug tracker (for example Jira) if the test failed.
NotesAnything else useful: screenshot name, browser, reason for a skip, retest date.

Status values and when to use each

Not runYou have not run this case yet. Use it as the starting value.
PassThe actual result matches the expected result.
FailThe actual result is different from the expected result. Log a bug and write its ID in Bug ID.
BlockedYou could not run the test because of something outside it, like the server being down or another bug stopping you. Write the reason in Notes.
SkippedYou decided not to run it this time, for example it is out of scope for this build. Write the reason in Notes.

Tip: write steps another person can follow

  • Write as if a new team member will run your test tomorrow without asking you anything.
  • Keep one action per step. Start each step with a verb: Open, Enter, Click, Select.
  • Name the exact button, field or link. Write Click “Login”, not “submit the form”.
  • Put real values in Test data, so anyone can repeat the test the same way.
  • Test one thing per test case. If you are checking two things, split them into two rows.
  • Make the expected result something you can see and check. “Works fine” is not an expected result.

Need more rows?

The table has space for 48 test cases. To add more, right-click a row number inside the table (not below it) and choose Insert. New rows inside the table keep the dropdowns, and the Summary counts them too.

The Summary sheet updates by itself

For the 8 examples, the Summary sheet shows:

5Pass
1Fail
1Blocked
1Not run
8Total
71%Pass rate
  • Counts come from the Status column (rows 7 to 54) on the Test cases sheet.
  • Executed counts every case except Not run, so Blocked and Skipped cases are included.
  • Pass rate = Pass divided by Executed. It shows 0.0% until you have run at least one case.

More templates

All files
TemplateRequirement traceability matrix (RTM) templateView TemplateTest plan templateView TemplateBug report templateView