Test Planning CTAL-AT Practice Questions (Page 5)

Questions 21–25

1. 21foundation · easy

   What is the main purpose of daily test planning in Agile?

   • ATo coordinate the day's testing tasks, prioritize them, and identify any impediments.
   • BTo assign test cases to testers for the entire iteration.
   • CTo create a detailed test plan for the entire release.
   • DTo review and update the iteration test plan.
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   What is a common content element of an Agile test plan?

   • AA detailed schedule of all test execution dates for the entire project.
   • BThe test approach, including the levels of testing and the types of tests to be performed.
   • CA list of all defects found in the previous release.
   • DA complete inventory of all test environments and their configurations.
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   How does an Agile test plan typically differ from a traditional test plan?

   • AIt contains a complete list of all test cases for the entire project.
   • BIt is written by the test manager and approved by the quality assurance department.
   • CIt is less detailed and focuses on the overall approach, with details added as needed.
   • DIt is a one-time, comprehensive document created before development starts.
   Reveal Solution Discussion Select an answer first
5. 24application · medium

   A team is planning a release that includes a new payment integration (high business risk) and several minor UI updates (low risk). The release test plan must be created with a risk-based approach. Which action best aligns with risk-based test estimation?

   • AAssign a higher proportion of test effort to the payment integration, with lighter regression for the UI updates.
   • BAllocate roughly equal test effort to the payment integration and the UI updates to ensure complete coverage.
   • CEstimate test effort primarily from the size of the user stories, using story points as the sole basis.
   • DDefer all test effort to the iteration level, since release-level planning cannot account for risk.
   Reveal Solution Discussion Select an answer first
6. 25application · medium

   During iteration planning, the team selects user stories and must decide how to test them. The product owner emphasizes a story that is technically complex but has low business risk. The team is cross-functional and includes testers. What is the most appropriate approach for iteration test planning?

   • ALet the testers independently create a detailed test plan for the entire iteration before development starts.
   • BHave the whole team collaboratively define test approaches and estimate effort for each story, adjusting as details emerge.
   • CDefer test planning until the daily stand-up, since iteration planning is only for development tasks.
   • DFocus test planning only on the technically complex story, as it is the hardest to test.
   Reveal Solution Discussion Select an answer first