Next Manual Testing batch starts October 2026 · Seats openBook free demo →
Tester AcademyBook free demo

Test Case Template (Free Download)

A ready test case template with all ten fields, plus a filled login-page example.

FreeNo sign-upUsed in our classes
.xlsx · 7 KB · Works in Excel, Google Sheets and LibreOffice
test-case-template.xlsxSheet 1 · 10 columns
fxTC_LOGIN_002
ABCD
1Test case IDDescriptionExpected resultStatus
2TC_LOGIN_001Valid email and passwordDashboard opensPass
3TC_LOGIN_002Wrong passwordError message shownPass
4TC_LOGIN_003Empty email fieldValidation message shownFail
5TC_LOGIN_004300-character emailInput rejected cleanlyBlocked
6TC_LOGIN_005SQL characters in emailInput rejected, no error pageNot run

What a test case template includes

A good test case template has ten fields. Here’s what goes in each, with an example.

Test case IDA unique, searchable ID.TC_LOGIN_001
DescriptionWhat the test checks, in one line.Wrong password shows an error
PrerequisitesWhat must be true before you start.User account exists
Test stepsNumbered actions, one per line.1. Open login 2. Enter email…
Test dataThe exact inputs you’ll use.priya@test.in / Wrong@123
Expected resultWhat should happen.Error: “Incorrect password”
Actual resultWhat did happen.Error shown as expected
StatusPass, fail, blocked or not run.Pass
Requirement IDThe requirement this test traces to.REQ-AUTH-04
PriorityHow critical the test is.High

Test case example: login page

Five test cases for one login screen, from the happy path to edge cases.

PassFailBlockedNot run
login-page-test-cases.xlsxSheet 1 · 10 columns
fxFail
ABCD
1Test case IDDescriptionExpected resultStatus
2TC_LOGIN_001Valid email and passwordDashboard opensPass
3TC_LOGIN_002Wrong passwordError message shownPass
4TC_LOGIN_003Empty email fieldValidation message shownFail
5TC_LOGIN_004300-character emailInput rejected cleanlyBlocked
6TC_LOGIN_005SQL characters in emailInput rejected, no error pageNot run

How to write a test case in 5 steps

Start from the requirement, end with a linked bug report.

  1. Read the requirementUnderstand what the feature must do, and note anything unclear before you start.
  2. List the scenariosWrite one line per thing to test: valid login, wrong password, empty fields, edge inputs.
  3. Write one test case per checkAdd the steps, test data and expected result, so anyone can run it the same way.
  4. Run it and record the resultFill in the actual result and the status: pass, fail, blocked or not run.
  5. Link failures to a bug reportFor every fail, raise a bug and add its ID, so the fix can be retested.

Test case vs test scenario

A scenario is what to test. A test case is exactly how to test it.

Answers: what to test

Test scenario

One line describing a situation to check. It’s broad, and one scenario usually becomes several test cases.

Example: Check login
Answers: how to test it

Test case

Steps, test data and the expected result, detailed enough that anyone runs it the same way.

Example: TC_LOGIN_002: enter a registered email and a wrong password, then expect “Incorrect password”.

FAQs

ID, description, prerequisites, steps, test data, expected result, actual result, status, requirement ID and priority.

Read the requirement, list the scenarios, then write one test case per check.

A scenario says what to test. A test case says exactly how to test it.

More free tools

Bug report templateExcel · Jira-ready fieldsGet it freeTest plan templateWord · Google DocsGet it freeSoftware testing MCQInstant score + explanationsStart the quiz

Learn to write these with a trainer

See the Manual Testing course

Stay in the loop

Get new batch dates on WhatsApp. One message when a batch opens, nothing else.

Stay in the loop
+91

By subscribing you agree to receive WhatsApp messages from Tester Academy. Read our Privacy policy.

WhatsAppBook free demo
Questions? WhatsApp us