Agile processes in QA world

Speaker: Inna Kozyreva

Transcript

1. Agile processes in QA world Inna Kozyreva
2. What is Agile?
3. Agile is an interactive software development methodology that promotes open collaboration and process adaptability through the life cycle of the project.
5. Sprint Planning Meeting • Highest priority stories are reviewed • Team selects stories • Team breaks stories down into tasks & team estimates
6. Product Backlog • Detailed Appropriately • Estimated • Emergent • Prioritized
8. - All team member describes: • What they did • What they plan to do • Issues/Blockers - Scrum Master tracks and resolve obstacles - 10-15 minutes Daily Stand-up
9. Сharacteristics of a good requirement: • Singularity • Completeness • Consistency • Traceability • Feasibility • Verifiability
10. Examples: 1. Add disclaimer "checkbox" for terms 2. When user checks the terms checkbox, activate the CONTINUE button, otherwise the CONTINUE button should be deactivated by default 3. When user clicks the CONTINUE button, should navigate to distribution.php 4. When user clicks the BACK button from distribution.php, return the user to the Final Proof
11. • Help improve efficiency by minimizing mistakes • Should be precise, efficient, easy to use in any situation • All the items on a good checklist should be actionable and grouped by category
12. Test Strategy in Agile - Participate in sprint planning - Estimate tasks - Write test cases using stories • High level test cases before coding begins - guide dev • Detailed test cases during coding - Functional tests ◦ Testing on dev. Bugs found and report immediately
13. - Pair test (Dev + QA) ◦ Performed when a part of a feature is implemented - Integration testing ◦ Performed on stage. Return task to dev for further fixing. - Regression testing ◦ Performed after code freeze for all entire project. - Sanity testing ◦ Performed after code pushed to prod. Errors found are logged in and prioritised during next sprint planning
14. - Team meets to review: • What went well • What did not go well • What we can improve - Team adds tasks for immediate actions for working better Sprint Retrospective
16. You have the right to: • bring up issues related to quality and process at any time • ask questions of customers and programmers and receive timely answers • ask for and receive help from anyone on the project team, including programmers, managers and customers
17. • make and update your own estimates for your own tasks and have these included in estimates for stories • the tools you need to do your job in a timely manner • expect your project team, not just yourself, to be responsible for quality
18. THANK YOU FOR ATTENTION!
19. Questions?!