What is a test plan and what should it contain?

• A. A document outlining scope, objectives, features tested, resources, schedule, risk, acceptance criteria, and test cases.
• B. A code module with implemented test functions.
• C. A user manual for the software.
• D. A log of all defects found.

Answer: (A)

A test plan is a formal document that describes how testing will be carried out. It should outline the project scope and testing objectives, specify which features will be tested, and identify the resources needed (people, environments, tools) along with the testing schedule. It also covers risk assessment to flag areas that may require extra attention, acceptance criteria that define what it means for testing to succeed, and the test cases or conditions that will be used to verify the software. Together, these elements provide a clear roadmap for the testing effort, helping teams coordinate, estimate effort, and manage risks.

Other artifacts serve different purposes: a code module with implemented test functions is the actual tests themselves, not the planning document; a user manual is for end users; and a defect log records issues found during testing.