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
In Behavior-Driven Development (BDD), what format are acceptance criteria typically written in?
Answer: Given-When-Then scenarios
BDD uses Given-When-Then (GWT) syntax to write executable specifications that serve as both documentation and automated tests.
A business analyst is facilitating a story mapping session. Where does validation fit in this activity?
Answer: Validation questions are embedded throughout — 'How will we know this works?'
Agile analysts embed validation thinking throughout story mapping by continuously asking how each story will be verified.
What is the primary difference between verification and validation in agile?
Answer: Verification checks if the product was built right; validation checks if the right product was built
Verification ensures the product conforms to specifications, while validation ensures it meets the actual needs of the users and stakeholders.
Which testing type focuses on ensuring that components work correctly together after integration?
Answer: Integration testing
Integration testing validates that multiple components or services interact correctly when combined.
A team wants to validate that a new feature meets user needs before full development. Which technique is MOST appropriate?
Answer: Usability testing with a prototype
Usability testing with a prototype allows teams to validate user needs cheaply before investing in full development.
What is 'continuous testing' in an agile/DevOps context?
Answer: Executing automated tests as part of every code commit in the CI/CD pipeline
Continuous testing means automated tests run automatically on every code change as part of the CI/CD pipeline, providing immediate feedback.
When should non-functional testing (performance, security) be addressed in agile?
Answer: As a continuous concern throughout the project, not deferred to the end
Non-functional requirements should be addressed continuously throughout delivery, not deferred, to avoid costly late-stage remediation.