Acceptance criteria: QA's quality boost

It's my presentation at Tokyo Test Fest 2024.11.15

Transcript

1. Acceptance criteria: QA's quality boost 2024.11.15 Tokyo Test Fest @____rina____
2. QA engineering manager 
 at Mercari　 
 
 🍜Fukuoka 
 
 Rina Fukuda @____rina____ 

4. QA engineering manager 
 at Mercari　 
 
 🍜Fukuoka 
 
 Rina Fukuda @____rina____ 

5. Our QA team's initiative We document test cases in our acceptance criteria and review them together as a team.
6. Challenges with the previous approach test cases user story acceptance criteria
7. PM Engineer Designer QA Impact - better for the whole team! The impact of this initiative helped the whole development team.
8. PM Easier for PMs! 🏝 🚤 🚢 Test Cases Acceptance Criteria
9. Engineer Helps Engineers!
10. Designer Good for Designers!
11. QA Better testing for QA!
12. PM Engineer Designer QA Better communication, smoother workflow 🏝
13. Deep dive
14. Three simple steps before after after ❶ combined test cases & acceptance criteria ❷ real-time reviews ❸ whole team participation
15. Unlocking the power of test cases
16. An overlooked treasure map: the untapped value of test cases test cases = treasure map user stories = islands
17. Signposts for everyone: acceptance criteria as guides ✅ can do ✅ cannot do ✅ testing details acceptance criteria = island sign
18. Example no test target condition expected result (✅or🛑) note 1 title and label display • title: ✅login • login label: ✅login 2 screen visibility with feature flag feature flag: on • ✅screen appears redirects to the home screen. 3 feature flag: off • ✅screen disappears 4 device compatibility • ✅iOS • ✅Android 🪧 ✅ can do ✅ cannot do ✅ testing details
19. Success! collaboration and quality improvement 🏝 🪧 🏝 🏝 🪧
20. Reviews: the key to quality
21. Three simple steps to effective reviews ❶ read out ❷ question ❸ check out 💬 ❓ ✅
22. From fuzzy requirements to clear acceptance criteria PM Designer Engineer QA spec UX/UI creation review of spec design doc acceptance criteria refinement (includes review of acceptance criteria)
23. Easy for everyone? can everyone do this?
24. How we started ❶ my scrum Team I started it in my scrum team. ❷ other scrum teams we expanded it to other scrum teams. ❸ many scrum teams now, many teams use it!
25. Why it works: shared understanding • We combine acceptance criteria and test cases. • Everyone sees the same information. • It’s easier to understand and discuss together!
26. What's next? • We are always improving this process. • We want to make it even better! • Try it in your teams!
27. Key takeaways Combine acceptance criteria and test cases Whole team review Improve quality together! 1 2 3