Project Work Products CT-AT Practice Questions (Page 4)

Questions 16–20

1. 16application · easy

   A tester is new to Agile and asks which artifacts are typically produced during a sprint to support testing. Which list correctly identifies the common project work products in an Agile project?

   • AA comprehensive requirements specification, a master test plan, and a test summary report.
   • BUser stories, acceptance criteria, test cases, test results, and defect reports.
   • CA project charter, a business case, and a risk register.
   • DA detailed design document, a database schema, and an API specification.
   Reveal Solution Discussion Select an answer first
2. 17application · medium

   A team uses a Kanban board to track work items. A tester is asked to test a user story that has just been moved to the 'Ready for Test' column. The story has no written acceptance criteria, only a title and a brief description. What is the most appropriate action for the tester?

   • AProceed with testing based solely on the story description and the developer's interpretation.
   • BWrite test cases based on common sense and industry standards for similar features.
   • CMark the story as 'blocked' and move on to other tasks until criteria are added.
   • DCollaborate with the product owner and developers to define acceptance criteria before starting test design.
   Reveal Solution Discussion Select an answer first
4. 18application · easy

   A tester is reviewing a user story that has the following acceptance criterion: 'Given a registered user, when they log in with valid credentials, then they are redirected to their dashboard.' Which type of test case should the tester derive from this criterion?

   • AA usability test that assesses the clarity of the login form.
   • BA performance test that measures login response time under load.
   • CA negative test that verifies the system rejects invalid credentials.
   • DA positive functional test that verifies successful login and redirection to the dashboard.
   Reveal Solution Discussion Select an answer first
5. 19foundation · easy

   How do user stories typically evolve during an Agile iteration?

   • AThey remain unchanged once they are added to the sprint backlog
   • BThey are only updated after the sprint review based on customer feedback
   • CThey are replaced by a detailed requirements specification at the start of the sprint
   • DThey are refined and clarified through team discussions and feedback, with acceptance criteria becoming more detailed as understanding grows
   Reveal Solution Discussion Select an answer first
6. 20expert · hard

   A team is developing a feature with a user story that has the acceptance criterion: 'Given a user has items in their cart, when they proceed to checkout, then they can enter a discount code.' The tester needs to design tests. The product owner clarifies that the discount code should only be valid for logged-in users. How should the tester update the test design?

   • AModify the existing test case to use a logged-in user and remove the guest user scenario.
   • BKeep the original test case as-is and add a note that the discount code feature is only for logged-in users.
   • CAsk the product owner to change the acceptance criterion to include the logged-in user constraint.
   • DAdd a new test case for a guest user attempting to enter a discount code, verifying it is rejected.
   Reveal Solution Discussion Select an answer first