How to Write Test Cases: Format, Examples and Best Practices

Every tester gets asked the same thing at some point: can you write test cases for this feature? If you are new, it is hard to know how to write test cases with the right level of detail, or where to start.

Knowing how to write test cases well saves time for the whole team. Good ones find bugs earlier, make regression runs repeatable and let a new colleague run your tests without asking questions.

This guide shows how to write test cases step by step, with a standard format, a login and a checkout example, a template you can copy and best practices used by QA teams.

What is a test case?

A test case is a documented check for one behaviour of the software. It states what to do, what data to use and what result to expect. The ISTQB glossary defines it as a set of preconditions, inputs, actions and expected results developed for a particular objective.

A test scenario is a high-level idea such as “user can log in”. A test case is a specific, runnable check under that scenario, such as “login fails with a wrong password”.

Standard test case format

Most teams use the same fields, whether they work in a spreadsheet or a test management tool.

How to write test cases step by step

1. Understand the requirement. Read the user story or spec and list the rules. Ask about anything unclear before you write a line.
2. List scenarios. Think about the happy path, error paths and edge cases.
3. Pick one behaviour per test case. If a title needs “and”, split it in two.
4. Write preconditions and test data. Use specific values, not “valid email”.
5. Write short, numbered steps using plain verbs: open, enter, click, select.
6. State a precise expected result. “Error message ‘Invalid password’ appears” beats “error shown”.
7. Review with a developer or peer to catch missing cases and wrong assumptions.

Test case examples

Example 1: login with valid credentials

Example 2: login with a wrong password

Example 3: checkout with an expired coupon

Preconditions: cart has one item and coupon SAVE10 expired yesterday. Steps: open the cart, enter SAVE10, click Apply. Expected result: a message says the coupon has expired and the cart total does not change.

Positive, negative and boundary test cases

When you plan how to write test cases for a feature, cover three groups:

• Positive: valid input produces the expected outcome.
• Negative: invalid, empty or malicious input is rejected safely.
• Boundary: values at the edge of a range, such as a password of exactly 8 characters when the minimum is 8.

For a field that accepts ages 18 to 60, test 17, 18, 60 and 61, plus an empty value and text such as “abc”.

Best practices for writing test cases

• Keep each test case independent, so one failure does not block the others.
• Use clear, consistent names so people can search and filter.
• Avoid vague words such as “properly” or “correctly” in expected results.
• Do not repeat steps that belong in preconditions.
• Link every test case to a requirement or user story for traceability.
• Review and retire outdated cases every sprint.
• Mark high-risk and frequently used flows as high priority and automate them first.

From manual test cases to automation

A well-written manual case becomes an automated test almost line by line. Here is TC_LOGIN_001 as a Playwright test (see the Playwright guide to writing tests):

import { test, expect } from '@playwright/test';

test('TC_LOGIN_001: registered user logs in', async ({ page }) => {
  await page.goto('/login');
  await page.getByLabel('Email').fill('user@example.com');
  await page.getByLabel('Password').fill('Secret123');
  await page.getByRole('button', { name: 'Log in' }).click();
  await expect(page).toHaveURL(/dashboard/);
});

Start by automating stable, high-value cases. Our guides on test automation tools, end to end testing best practices and API testing with Postman show where to go next.

Final thoughts

Learning how to write test cases is mostly about clarity: one behaviour, exact data and a precise expected result. Use the format above, cover positive, negative and boundary inputs, and get a peer review. Start with the template for your next story and refine it as your team learns what works.

Frequently asked questions

Keep learning