Testing and Development Activities CT-AT Practice Questions (Page 7)

Questions 31–35

1. 31application · medium

   A team is starting a new sprint to implement a login feature. The product owner has provided a high-level requirement: 'Users must be able to log in with their email and password.' The team wants to clarify the expected behavior before writing any code. Which approach best supports this goal?

   • AImplement the login code first, then write unit tests to verify the implementation.
   • BAsk the product owner to write detailed user stories with all edge cases before the sprint begins.
   • CWrite a set of acceptance tests that specify valid and invalid login attempts, then implement the code to pass those tests.
   • DCreate a prototype and ask the product owner to try it manually after the sprint.
   Reveal Solution Discussion Select an answer first
2. 32expert · medium

   A team is adopting BDD and has written feature files with scenarios. However, the scenarios are too long and complex, making them difficult to maintain. What is the best practice to address this?

   • ABreak down complex scenarios into smaller, focused scenarios that each test one behavior.
   • BCombine multiple behaviors into a single scenario to reduce the number of files.
   • CWrite scenarios in a technical language to be more precise.
   • DRemove scenarios that are difficult to automate.
   Reveal Solution Discussion Select an answer first
4. 33expert · hard

   A team's CI pipeline runs a full regression suite on every commit, but the suite takes 45 minutes, slowing down feedback. Developers are tempted to skip running tests locally. What is the best approach to maintain fast feedback while ensuring quality?

   • AReduce the regression suite to only the most critical tests to make it faster.
   • BImplement a staged pipeline: run fast unit tests on every commit, and run slower integration and regression tests on a scheduled or merge basis.
   • CIncrease the number of CI servers to run the full suite in parallel.
   • DRun the full suite only on nightly builds and rely on manual testing during the day.
   Reveal Solution Discussion Select an answer first
5. 34application · medium

   A product owner describes a new search feature: 'Users should be able to search by keyword and see relevant results.' The team wants to turn this into an executable specification. What should they do first?

   • ACollaboratively write acceptance tests that define examples of valid searches and expected results.
   • BStart coding the search algorithm and write tests later.
   • CAsk the product owner to provide a detailed technical design document.
   • DCreate a prototype and have the product owner test it manually.
   Reveal Solution Discussion Select an answer first
6. 35foundation · easy

   How do testers typically collaborate with developers in agile development?

   • ATesters only interact with developers when a defect is found.
   • BTesters work independently and hand over test results to developers at the end of each iteration.
   • CTesters work alongside developers, providing continuous feedback and helping to clarify requirements.
   • DTesters are responsible for writing all the code, so developers can focus on testing.
   Reveal Solution Discussion Select an answer first