← Back to Kit Home

Test Case Template

Copy the template below for every new test case. Then look at the 3 filled examples.

---

Empty Template

Field	Value
Test Case ID	TC-001
Title	Short, clear description of what is tested
Module / Feature	e.g. Login, Checkout, Search
Preconditions	What must be true before the test starts
Test Data	Usernames, passwords, files, etc.
Steps	1. ... 2. ... 3. ...
Expected Result	What should happen
Actual Result	What really happened (fill during execution)
Status	Not Run / Pass / Fail / Blocked
Priority	High / Medium / Low
Notes	Anything else (bug ID, environment, etc.)

---

Writing good steps — quick rules

• Start from a known state (e.g. "User is on the login page").
• One action per step.
• Include exact test data.
• The expected result must be checkable — you can say "Pass" or "Fail" without discussion.

---

Example 1 — Login with valid credentials

Field	Value
Test Case ID	TC-LOGIN-001
Title	Login with valid email and password
Module / Feature	Login
Preconditions	User account exists: user@test.com / Pass123!. App is open on the login page.
Test Data	Email: user@test.com, Password: Pass123!
Steps	1. Open https://app.example.com/login 2. Enter "user@test.com" in the Email field 3. Enter "Pass123!" in the Password field 4. Click the "Log in" button
Expected Result	User is logged in and redirected to the Dashboard page. "Welcome, Test User" message is shown in the header.
Actual Result	As expected
Status	Pass
Priority	High
Notes	Tested on Chrome 126, staging, build 2.4.1

---

Example 2 — Login with wrong password (negative test)

Field	Value
Test Case ID	TC-LOGIN-002
Title	Login with valid email and wrong password shows an error
Module / Feature	Login
Preconditions	User account exists: user@test.com / Pass123!. App is open on the login page.
Test Data	Email: user@test.com, Password: WrongPass99
Steps	1. Open https://app.example.com/login 2. Enter "user@test.com" in the Email field 3. Enter "WrongPass99" in the Password field 4. Click the "Log in" button
Expected Result	User is NOT logged in. Error message "Invalid email or password" is shown. Password field is cleared. User stays on the login page.
Actual Result	Error message is shown, but password field is NOT cleared
Status	Fail
Priority	High
Notes	Bug reported: BUG-114

---

Example 3 — Empty password field (validation test)

Field	Value
Test Case ID	TC-LOGIN-003
Title	Login button is disabled when password field is empty
Module / Feature	Login
Preconditions	App is open on the login page.
Test Data	Email: user@test.com, Password: (empty)
Steps	1. Open https://app.example.com/login 2. Enter "user@test.com" in the Email field 3. Leave the Password field empty 4. Look at the "Log in" button
Expected Result	"Log in" button is disabled (grey). A hint "Password is required" is shown under the password field.
Actual Result	As expected
Status	Pass
Priority	Medium
Notes	—

---

💡 Tip: Group test cases by feature (e.g. all TC-LOGIN- together). A group of test cases is called a test suite*.