QA in Agile

Alyona Gavrylei, Competence Group Manager of QA, QA engineer, MEV, LLC

Transcript

1. QA in Agile
2. Agenda 1. QA role in Agile real world. 2. QA role in Agile events. 3. Agile test automation. 4. QA Responsibilities in project. 5. Real examples on project.
3. QA in Agile | Waterfall process
4. QA in Agile | Agile process
5. QA in Agile | But what exactly is the role of QA in Agile? 1. Attend daily stand-ups. QA discusses what got accomplished in the previous day, what will be the focus of work today, and if they have any obstacles that need to be removed.
6. QA in Agile | But what exactly is the role of QA in Agile? 2. Attend sprint-planning sessions. QA helps to determine the Sprint scope.
7. QA in Agile | But what exactly is the role of QA in Agile? 3. Don’t save all the testing for the end. Test throughout the sprint.
8. QA in Agile | But what exactly is the role of QA in Agile? 4. Meet with developers for short hand-off demonstrations.
9. QA in Agile | But what exactly is the role of QA in Agile? 5. Attend sprint retrospectives.
10. QA role in Agile events | Sprint Retrospective QA should prepare a feedback about how sprint went.
11. QA role in Agile events | Sprint Review Sprint Review = visualization of team efforts during the Sprint.
12. QA in Agile | But what exactly is the role of QA in Agile? 6. Document test cases.
13. QA in Agile | QA role in Agile real world Следует выполнять исследовательское и ручное тестирование, когда все пользовательские истории закончены. Это не только поможет обнаружить баги, но и покажет, какие тесты стоит автоматизировать в следующих спринтах.
14. QA in Agile | QA role in Agile real world Автоматизированное тестирование играет ключевую роль для гибкой разработки. Автотесты предупреждают возникновение множества проблем и помогают сэкономить время.
15. QA in Agile | User story & QA Lifecycle of a story from a QA perspective
16. QA in Agile | Breadth and Depth of the Role Who can be QA in your team?
17. QA in Agile | Principles of Test Automation
18. QA in Agile | Why we start automation? 1. Manual test execution takes too long. 2. People can make a mistake. 3. Frees up time for the team to solve complex problems. 4. Provide information about the application quickly. 5. Tests are a good kind of documentation.
19. QA in Agile | Problems during implementation 1. Tests can not be automated, using only free time, it is necessary to engage fully. 2. Initial contribution. 3. Lack of experience. 4. He loses the experience of the main profession if someone begins to engage autotests.
20. QA in Agile | Problems during implementation 5. Fear - main fear that it will not work, will take time, and the product is necessary to take. 6. Deal with automation for automation, and not for the improving the quality of the product. 7. Focus on technical automation problems also leads to loss goal - why auto-tests are written.
21. QA in Agile | Testing pyramid
22. QA in Agile | Principles to keep in mind 1. Test automation cannot duplicate human testers. 2. Test automation is more than test execution. 3. Test automation is vulnerable to instant obsolescence.
23. QA in Agile | Principles to keep in mind 4. Test tools are many and varied. 5. Test automation can distract you from good testing.
24. QA Responsibilities The main responsibility of QA team is to ensure that the released product satisfies the quality criteria described in test plan.
25. Kanban Kanban is a method for managing the creation of products with an emphasis on continual delivery while not overburdening the development team.
26. Scrum | Developers board
27. Kanban | QA Board
28. Kanban | Project workflow
29. Kanban | The benefits of Kanban • Planning flexibility; • Shortened cycle times; • Fewer bottlenecks; • Visual metrics; • Continuous delivery.
30. Questions?