โ† All AAC Flashcard Decks

Agile Testing & Validation Flashcards

7 cards from real AAC practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Agile Testing & Validation flashcards as text
  1. A team finds the same defect type repeatedly across sprints. What is the BEST long-term agile response?

    Answer: Raise it in the retrospective and add automated checks to prevent recurrence

    Retrospectives are the right forum to address recurring defect patterns, leading to systemic fixes like automated checks or process improvements.

  2. What does 'done means tested' imply about the agile team's culture?

    Answer: Quality is built in continuously and testing is integral to completing any work item

    'Done means tested' reflects a whole-team quality mindset where testing is not a separate phase but integral to completing every increment.

  3. Which agile artifact BEST communicates the expected behavior of a feature to both business and technical stakeholders?

    Answer: Executable acceptance tests written in BDD format

    BDD-style executable acceptance tests serve as living documentation that is understandable by both business and technical audiences.

  4. A team is practicing ATDD. At what point should acceptance tests ideally be written?

    Answer: Before coding begins, as part of story refinement

    In ATDD, acceptance tests are written before development begins, driving the implementation and ensuring alignment on expected outcomes.

  5. What is 'test coverage' in the context of agile, and why must it be used carefully?

    Answer: The percentage of lines of code executed by tests; it measures quantity, not quality or risk coverage

    Code coverage measures what percentage of code is executed by tests, but high coverage doesn't guarantee meaningful tests or that the right things are being tested.

  6. Which of the following BEST describes 'testability' as a quality attribute in agile analysis?

    Answer: The degree to which requirements and code can be verified through testing

    Testability refers to how easily requirements and the resulting software can be verified, which is influenced by clarity, modularity, and observability.

  7. A business analyst notices that user stories frequently fail UAT due to ambiguous acceptance criteria. What is the BEST corrective action?

    Answer: Conduct more thorough Three Amigos sessions to clarify acceptance criteria before sprint start

    Three Amigos sessions before sprint start surface ambiguities in acceptance criteria early, reducing UAT failures caused by misunderstood requirements.