How to Write Test Cases: Step-by-Step Template and Examples

Introduction

Clear test cases help teams at Cinute Digital Pvt Ltd (CDPL) move fast without breaking quality. A good test case is easy to read, repeatable by anyone on the team, and tied to a requirement or risk. This guide shows the anatomy, good vs bad examples, a copy ready template, common mistakes to avoid, and practical QA tips.

Anatomy of a High Quality Test Case

• ID: unique and meaningful, for example TC-LOGIN-001.
• Title: short action oriented description.
• Purpose or Requirement ID: trace to user story or spec.
• Preconditions: state, role, or data required before running.
• Test Data: concrete values and boundary values.
• Steps: numbered actions a tester can follow without guessing.
• Expected Result: observable outcome that proves success or failure.
• Priority and Tags: risk, module, release, smoke or regression.
• Attachments or Evidence: screenshots, logs, or recordings when needed.

Good vs Bad Test Case Examples

Login example

Bad
Title: Login
Steps: Try to login
Expected: Works

Good
ID: TC-LOGIN-001
Title: Login with valid email and password
Requirement: REQ-AUTH-01
Preconditions: user exists and is verified
Data: email user@test.com, password Passw0rd!
Steps:
  1. Open /login
  2. Enter email user@test.com
  3. Enter password Passw0rd!
  4. Click Sign in
Expected:
  - User is redirected to /dashboard
  - Profile name is visible in header

Specific steps and outcomes remove ambiguity

Checkout example

Bad
Title: Checkout
Steps: Buy item
Expected: Success

Good
ID: TC-CHK-002
Title: Checkout with saved address and valid card
Requirement: REQ-CHK-01
Preconditions: user logged in, cart has 1 item, saved address exists
Data: Visa 4111 1111 1111 1111, Exp 12/30, CVV 123
Steps:
  1. Open /checkout
  2. Select saved address
  3. Choose Card payment
  4. Enter card number, expiry, CVV
  5. Click Pay
Expected:
  - Order confirmation shows Order ID
  - Email receipt sent within 60 seconds

Good cases are deterministic and verifiable

Free Test Case Template

Use this lightweight template in your test management tool or spreadsheet.

ID:
Title:
Requirement:
Module:
Priority: High | Medium | Low
Tags: Smoke, Regression, Security, Performance
Preconditions:
Data:
Steps:
Expected Result:
Notes:
Attachments:

Minimal template that fits most projects

Tip for CDPL learners: keep IDs stable across releases and add a changelog note when steps or expected results change.

Common Mistakes to Avoid

• Vague steps: write actions a new tester can follow.
• Multiple outcomes in one case: split into separate cases.
• No test data: add real and boundary values.
• Missing traceability: always link to a story or requirement ID.
• Unmaintained suites: review and retire duplicates every release.

QA Tips that Raise Quality

• Start with smoke coverage: a small set that runs on every build.
• Use a checklist for consistency: preconditions, data, steps, expected result, and evidence.
• Pair on first runs: author and reviewer execute once to validate clarity.
• Track status with a matrix: map cases to requirements and show pass or fail per release.
• Promote high value cases to automation: focus on stable critical paths like login and checkout.

Conclusion

Great test cases are short, clear, and repeatable. Use the template, model your writing on the good examples, and link every case to a requirement so leaders can see coverage at a glance. With these habits, CDPL learners and partner teams can collaborate smoothly and ship reliable features.