Home › Software Testing › Software Testing › fundamentals_levels_techniques › A test plan typically describes
A test plan typically describes
AScope, approach, resources and schedule
BOnly names of testers on the project
COnly bug reports raised during cycles
DOnly source code structure of system
Answer & Solution
Correct answer: A. Scope, approach, resources and schedule
IEEE 829 / ISTQB test plan: scope, objectives, approach, schedule, resources, entry/exit criteria, risks. It is the management blueprint, not a defect log.
Related questions
Exit criteria for a test phase typically includeTest-driven development (TDD) follows the cycleIn Agile, the tester's role is BEST described asSelenium is BEST described asWhich is a recognised BENEFIT of test automation?Risk-based testing prioritises test effort byA defect lifecycle typically begins with statusBranch (decision) coverage requires