Using Shift Left to Improve Test Basis Quality CTAL-AT Practice Questions (Page 5)

Questions 21–25

1. 21foundation · easy

   How can testers contribute to improving test basis quality by being involved early in user story creation?

   • ABy writing the user stories themselves to ensure they are complete
   • BBy focusing only on the technical implementation details
   • CBy asking clarifying questions to make acceptance criteria more specific and testable
   • DBy waiting until the story is fully developed before reviewing it
   Reveal Solution Discussion Select an answer first
2. 22application · medium

   A team is struggling with stories that are interpreted differently by developers and testers. To improve the test basis, they decide to use specification by example. What is the primary benefit of this collaborative practice?

   • AIt ensures that all stories are estimated in the same way, improving velocity predictability.
   • BIt replaces the need for a Definition of Ready by making stories self-explanatory.
   • CIt provides concrete, executable examples that clarify expected behavior and serve as the basis for both development and testing.
   • DIt automates the creation of all test cases, eliminating the need for manual test design.
   Reveal Solution Discussion Select an answer first
4. 23foundation · easy

   During backlog refinement, what is a valuable tester activity to improve test basis quality?

   • AEstimating the development effort for each story
   • BWriting the final test report for the story
   • CIdentifying missing acceptance criteria and suggesting additional testable conditions
   • DAssigning the story to a specific developer
   Reveal Solution Discussion Select an answer first
5. 24application · medium

   After a sprint, the team notices that several stories were rejected by the product owner because the acceptance criteria were misinterpreted. To prevent this from recurring, what is the most effective feedback loop to establish?

   • AA sprint retrospective where the team discusses the misinterpretations and agrees to use specification by example in future backlog refinement.
   • BA post-mortem analysis of the rejected stories to assign blame to the developer or tester.
   • CA request to the product owner to write more detailed stories in the future.
   • DA daily stand-up meeting where the team reports on their progress.
   Reveal Solution Discussion Select an answer first
6. 25application · medium

   A team is having difficulty with stories that are too large and complex to estimate. They want to use the 'three amigos' practice to break them down. What is the primary role of the tester in this collaborative session?

   • ATo estimate the effort required for testing each of the smaller stories.
   • BTo prioritize the smaller stories based on business value.
   • CTo ensure that the stories are broken down into smaller, testable increments and that acceptance criteria are defined for each.
   • DTo write the code for the smaller stories to prove they are feasible.
   Reveal Solution Discussion Select an answer first