Test Plan Writing
5 exercises — practise writing professional scope sections, entry/exit criteria, objectives, risk entries, and suspension criteria in English.
0 / 5 completed
Quick reference: Test Plan vocabulary
- Scope — what is included and explicitly excluded from testing
- Entry criteria — measurable conditions that must be met before testing begins
- Exit criteria — measurable conditions that define when testing is complete
- Risk + Mitigation — a named threat paired with a concrete plan to reduce its impact
- Suspension / Resumption criteria — thresholds for pausing and restarting testing
1 / 5
A QA lead is writing the Scope section of a test plan for a new checkout module. Which statement best represents how the "out of scope" sub-section should be written?
Out-of-scope items must be explicitly named and explained.
Options A and D are too vague and incomplete. Option B is conversational — "we won't test everything" is ambiguous and unprofessional. Option C uses the standard structure: a clear list of excluded areas with a note about where they will be addressed, preventing scope ambiguity and managing stakeholder expectations.
Key vocabulary:
• Out of scope — formally excluded from the current test effort; must be explicitly listed
• Scope creep — uncontrolled expansion of testing beyond agreed boundaries
• Dedicated test plan — a separate document for a specific testing concern (performance, security)
• Stakeholder expectations — the assumptions of those who authorized and will review the testing effort
Options A and D are too vague and incomplete. Option B is conversational — "we won't test everything" is ambiguous and unprofessional. Option C uses the standard structure: a clear list of excluded areas with a note about where they will be addressed, preventing scope ambiguity and managing stakeholder expectations.
Key vocabulary:
• Out of scope — formally excluded from the current test effort; must be explicitly listed
• Scope creep — uncontrolled expansion of testing beyond agreed boundaries
• Dedicated test plan — a separate document for a specific testing concern (performance, security)
• Stakeholder expectations — the assumptions of those who authorized and will review the testing effort