QA and test automation

Stage 2 · Lesson 3 of 8

Test cases and checklists

Manual testing done well

A is a written test with an ID, a title, (what must be true before you start), steps, test data and an expected result. Anyone can run it and reach the same verdict. A checklist is a shorter list of things to verify, and it trusts the tester to work out the steps.

Many modern teams prefer checklists because they are faster to write and cheaper to keep up to date. Use detailed cases where precision matters: payments, regulated industries, or handing work to someone new. Use checklists elsewhere.

Either way, each item should check one thing and have a clear expected result. Your regression cases, the checks that old features still work, will be the first you automate later, so writing them clearly now saves time.

Common trapa case that says "verify the page works", which two testers will judge differently.

A question to check yourself, an AI practice session and 1 cheat sheet entry come with the full roadmap. Unlock

Resources for this stage

Start with

Practise

Keep handy

  • The largest testing community: free Club forum and articles on exploratory testing, charters and bug advocacy

Also worth your time

Mark this stage as not done?