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.
DescriptionWhat the test checks, in one line.
PrerequisitesWhat must be true before you start.
Test stepsNumbered actions, one per line.
Test dataThe exact inputs you’ll use.
Expected resultWhat should happen.
Actual resultWhat did happen.
StatusPass, fail, blocked or not run.
Requirement IDThe requirement this test traces to.
PriorityHow critical the test is.
Test case example: login page
Five test cases for one login screen, from the happy path to edge cases.
How to write a test case in 5 steps
Start from the requirement, end with a linked bug report.
- Read the requirementUnderstand what the feature must do, and note anything unclear before you start.
- List the scenariosWrite one line per thing to test: valid login, wrong password, empty fields, edge inputs.
- Write one test case per checkAdd the steps, test data and expected result, so anyone can run it the same way.
- Run it and record the resultFill in the actual result and the status: pass, fail, blocked or not run.
- 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 loginAnswers: 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”.Stay in the loop
Get new batch dates on WhatsApp. One message when a batch opens, nothing else.
By subscribing you agree to receive WhatsApp messages from Tester Academy. Read our Privacy policy.

