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

Questions 36–40

1. 36foundation · easy

   What is the primary purpose of Acceptance Test-Driven Development (ATDD)?

   • ATo automate all unit tests before coding begins.
   • BTo test the system after development is complete to ensure it meets the original requirements.
   • CTo replace all manual testing with automated acceptance tests.
   • DTo use acceptance tests as a way to clarify requirements and drive the development of features.
   Reveal Solution Discussion Select an answer first
2. 37foundation · easy

   How are testing activities typically integrated into an agile iteration?

   • ATesting is done only by the testers, who work separately from the development team.
   • BTesting is only done if there is time left after development is finished.
   • CTesting is planned and executed continuously throughout the iteration, with testers involved from the start.
   • DTesting is performed only at the end of the iteration, after all development is complete.
   Reveal Solution Discussion Select an answer first
4. 38expert · hard

   A tester and a developer disagree on whether a defect is a real issue or a misunderstanding of the requirements. The product owner is unavailable. What is the best way to resolve this?

   • ALog the defect and move on without resolution.
   • BLet the developer decide, since they wrote the code.
   • CDiscuss the issue with the whole team, including the product owner if possible, and use the acceptance criteria as the basis for the decision.
   • DLet the tester decide, since they found the issue.
   Reveal Solution Discussion Select an answer first
5. 39application · medium

   A team is deciding which tests to automate first. They have limited time and want to maximize the value of automation. Which test suite should they prioritize?

   • AAll tests, including those that are highly unstable.
   • BThe tests that are easiest to automate, regardless of their importance.
   • CThe regression tests that are run most frequently and are critical to business functionality.
   • DThe tests that are rarely run but cover edge cases.
   Reveal Solution Discussion Select an answer first
6. 40foundation · easy

   What is the typical sequence of steps in Test-Driven Development (TDD)?

   • AWrite a passing test, write code to make it fail, then fix the test.
   • BWrite the production code, then write tests to verify it, then refactor the tests.
   • CWrite all tests upfront, then write all code, then run the tests once at the end.
   • DWrite a failing test, write the minimum code to pass the test, then refactor the code.
   Reveal Solution Discussion Select an answer first