AAC Agile Testing & Validation 3 — Questions and Answers
Question 1: In Behavior-Driven Development (BDD), what format are acceptance criteria typically written in?
- Use case narratives
- Given-When-Then scenarios (Correct answer)
- Decision tables
- State transition diagrams
Correct answer: Given-When-Then scenarios
BDD uses Given-When-Then (GWT) syntax to write executable specifications that serve as both documentation and automated tests.
Question 2: A business analyst is facilitating a story mapping session. Where does validation fit in this activity?
- Only after the map is finalized
- Validation questions are embedded throughout — 'How will we know this works?' (Correct answer)
- Validation is handled separately by the QA team after the session
- Validation occurs only for backbone-level stories
Correct 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.
Question 3: What is the primary difference between verification and validation in agile?
- Verification checks if the product was built right; validation checks if the right product was built (Correct answer)
- Verification is done by QA; validation is done by developers
- Verification happens in production; validation happens in staging
- They are synonymous terms in agile
Correct 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.
Question 4: Which testing type focuses on ensuring that components work correctly together after integration?
- Unit testing
- Smoke testing
- Integration testing (Correct answer)
- Acceptance testing
Correct answer: Integration testing
Integration testing validates that multiple components or services interact correctly when combined.
Question 5: A team wants to validate that a new feature meets user needs before full development. Which technique is MOST appropriate?
- Full regression testing
- Usability testing with a prototype (Correct answer)
- Load testing in production
- Code review
Correct answer: Usability testing with a prototype
Usability testing with a prototype allows teams to validate user needs cheaply before investing in full development.
Question 6: What is 'continuous testing' in an agile/DevOps context?
- Running tests 24 hours a day manually
- Executing automated tests as part of every code commit in the CI/CD pipeline (Correct answer)
- Performing exploratory testing continuously throughout the sprint
- Having testers attend all daily standups
Correct 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.
Question 7: When should non-functional testing (performance, security) be addressed in agile?
- Only in a dedicated hardening sprint before release
- As late as possible to avoid slowing down feature delivery
- As a continuous concern throughout the project, not deferred to the end (Correct answer)
- Only when explicitly requested by the Product Owner
Correct 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.
AAC Agile Testing & Validation 3
In Behavior-Driven Development (BDD), what format are acceptance criteria typically written in?