Learner can write a clear test case with preconditions, steps and an expected result, and tell a checklist from a test case from a scenario.
Test artifacts: from plan to case
Test artifacts: from plan to case
A test plan is a high-level document describing the scope, approach, resources and schedule for a testing effort. It answers 'what, why, how and when'. Below the plan sit three lighter artifacts that testers use day to day.
A checklist is a simple list of reminders — things to check without detailed steps. It is fast to write, great for exploratory sessions, but leaves too much to the individual tester's interpretation. Example: '[ ] Login page loads [ ] Password field masks input [ ] Error message appears on wrong password'.
A test scenario is a high-level statement of a user flow to be tested end-to-end. Example: 'Verify that a registered user can log in and see their dashboard.' It covers the 'what' but not every click.
A test case is the most detailed artifact. It contains: a unique ID and title, preconditions (the state the system must be in before the test), numbered step-by-step actions, expected result for each step or the whole case, and optionally test data. A good test case is atomic (tests exactly one thing), repeatable (any tester gets the same result), and unambiguous (no guessing required). A vague test case — 'Check that login works' — fails all three criteria.
Lesson notes
Test artifacts: from plan to case
A test plan is a high-level document describing the scope, approach, resources and schedule for a testing effort. It answers 'what, why, how and when'. Below the plan sit three lighter artifacts that testers use day to day.
A checklist is a simple list of reminders — things to check without detailed steps. It is fast to write, great for exploratory sessions, but leaves too much to the individual tester's interpretation. Example: '[ ] Login page loads [ ] Password field masks input [ ] Error message appears on wrong password'.
A test scenario is a high-level statement of a user flow to be tested end-to-end. Example: 'Verify that a registered user can log in and see their dashboard.' It covers the 'what' but not every click.
A test case is the most detailed artifact. It contains: a unique ID and title, preconditions (the state the system must be in before the test), numbered step-by-step actions, expected result for each step or the whole case, and optionally test data. A good test case is atomic (tests exactly one thing), repeatable (any tester gets the same result), and unambiguous (no guessing required). A vague test case — 'Check that login works' — fails all three criteria.