Qa role in agile teams
1 like197 views
This document discusses the role of QA in agile teams. It begins with an overview of agile methods and quality before comparing the traditional QA role to the agile QA role. In agile, QA is an integral part of the development team. The document then outlines the responsibilities of QA in agile teams such as helping define user stories, participating in planning and estimates, conducting sashimi acceptance testing, automating test cases, and providing continuous feedback. It concludes by discussing common mistakes made with QA in agile.
Qa role in agile teams
- 1. QA Role In Agile Teams SOFTWARE ENGINEERING – CAPSTONE PROJECT ANWAR SADAT
- 2. Capstone Project 2017 2 Today’s Discussion • Agile Methods and Quality • Comparison of QA in Traditional versus Agile • Agile QA Responsibilities • Common Mistakes • Conclusion
- 3. Capstone Project 2017 3 Agile Methods and Quality Agile principle #9: “Continuous attention to technical excellence and good design enhances agility.” Technical excellence is achieved in many ways, but all include a constant focus on quality. Observation: Agile projects emphasize quality much more than traditional.
- 4. Capstone Project 2017 4 Agile Methods and Quality HOW TO APPLY IT?
- 5. Applying Agile to QA
- 6. Capstone Project 2017 Comparison QA testers are integral part of development team TRADITIONAL AGILE QA is separate team QA to Dev: “You write buggy software!” Dev to QA: “You’re not good enough to be a software developer!” “I am part of the development team with specialized expertise in delivering quality.” “What can I do to help?”
- 7. Capstone Project 2017 7 Comparison Test continuously, as early as possible AGILE Test at end TRADITIONAL
- 8. Capstone Project 2017 8 Comparison Rely on conversations & shared knowledge AGILE Rely on documents TRADITIONAL
- 9. Capstone Project 2017 9 Comparison Test functional slices iteratively AGILE Test full system TRADITIONAL Iteration 2 Iteration 1 Iteration 3
- 10. Capstone Project 2017 10 Comparison Dev Test Requirement specs, detail designs, full system code Test plans, bug reports User stories Acceptance test cases Automation scripts Functional slice testing Unofficial testing Wikis Daily synchronization Face-to-face conversations about bugs Artifact Handoffs TRADITIONAL AGILE Holistic Development
- 11. Capstone Project 2017 11 Comparison Conformance to Plan TRADITIONAL AGILE Emergent Goals A - Start B - Planned Result The Plan C – Relevant Goal • Verify conformance to original plan • Write bugs to direct path back to plan • Welcome change • Verify relevant goals • Write bugs to enforce emergent plan and changed requirements
- 12. Capstone Project 2017 12 Comparison Automate all levels – unit, functional, integration, release, and regression TRADITIONAL AGILE Lots of manual testing, automate regression suite if possible
- 13. Capstone Project 2017 13 Comparison TRADITIONAL AGILE Hiring – testers that are good at writing test plans and executing test cases Hiring – testers skilled in automation, scripting, selecting right tool for current needs
- 14. Capstone Project 2017 14 Comparison Hiring – testers that have a knack for collaboration and team-based accountability TRADITIONAL AGILE Hiring – testers that can take their assignment and run with it
- 16. Capstone Project 2017 16 User Stories • Help customer/team develop user stories • Assist customer/proxy in defining acceptance criteria • When I select the Pending Loans menu item, I expect a new window with pending loans. • When I select the Pending Loans menu item, I expect to see only pending loans for me. • When I close the window, I expect to be taken back to the Main window. View Pending Loans As a loan rep, I want to see all pending loans, so that I have a visual reminder of follow-up calls.
- 17. Capstone Project 2017 17 Product Backlog and Estimates • Offer up items to product backlog • Ensure testing effort is accounted for in user story estimates Priority Item # Description Estimate Sprint Urgent 1 User login 2 1 2 Establish development environment 13 1 3 Display main window 8 1 4 Record video 40 5 Connect to video feeds 8 High 6 Change video feeds 13 7 Establish test automation harness 20 8 Zoom camera 5 9 Research competition 20 1 Med 10 Tile video feeds onto single screen 40 11 Regression test legacy SW components 40 12 Configure system 20 13 Playback video 13 QA-specific line items
- 18. Capstone Project 2017 18 Sprint Backlog and Estimates • Ensure test efforts are accounted for as sprint backlog tasks • Participate in sprint planning and release planning QA-specific line items Who Description Estimate (Hours) Remaining (Hours) Notes User login Chris Login window 8 4 Hide password 2 2 John Verify login id is correct 16 0 i/f with Security system John Verify password is correct 16 12 i/f with Security system Acceptance testing 8 8 Chris Block after 3 incorrect tries 24 0 Log occurrence to "watch file" Mary Test case automation 24 8 Display main window Bala, Tim Query DB for video connections 32 0 Bala to do DB arch Tim Establish connections 16 16 Ralph Regress legacy DB 64 48 Total hours 210 98 Total relative points from product backlog 32 32 Team members with QA expertise
- 19. Capstone Project 2017 19 Definition of Done • Ensure that a solid “definition of done” is developed up front, for example: • All new/modified code reviewed • Coding standards compliance • Static purification with 0 errors and 0 warnings • Dynamic purification – no memory leaks • All methods <= cyclomatic complexity 10 • All code checked in to Subversion prod branch • 80% code coverage – unit testing • Zero known bugs • Acceptance tests verified by QA on clean system • Acceptance tests verified by customer or proxy
- 20. Capstone Project 2017 20 Sashimi Acceptance Testing • Verify functional slices • Verify user stories satisfy acceptance test cases • Adhere to definition of done • Verify incremental integration • “Unofficial” testing for feedback • Exploratory testing Iteration 2 Iteration 1 Iteration 3
- 21. Capstone Project 2017 21 Sashimi Acceptance Testing Deliver multiple times to QA in a sprint Dev concentrates on bugfixes several days prior to sprint end QA writes additional tests and creates automation http://edgehopper.com/qatesting-in-an-agile-environment/ QA wraps up with final acceptance QA assists iteration planning QA tests and gives feedback QA tests and gives feedback
- 22. Capstone Project 2017 22 Test Case Automation • Choose appropriate tool for your needs • Leverage previous experience and use of tools • Focus on user actions and expected results for acceptance test cases • Anticipate what the result might look like - Screen mocks - Design diagrams - Collaborative discussions • Code the automation script • Run it prior to receiving the software - Verify the test case fails - Prevents the test case from accidentally passing - Similar to TDD • Once software is received, verify the test case works
- 23. Capstone Project 2017 23 Popular Tools for Test Case Automation Unit Testing / TDD • xUnit • UnitTest++ • Jtest • utMySQL • Etc. Sashimi / Integration / Release / Regression • FitNesse (open source) • Selenium (open source) • CruiseControl (CI) • Watij, Watir, Watin (open source) • TestComplete (by AutomatedQA) • Quick Test Pro (HP Mercury) • WinRunner (HP Mercury) • LoadRunner (HP Mercury) • SilkTest (Borland) • Etc.
- 24. Capstone Project 2017 24 Release Testing • Integration of multiple sprint’s functional slices • Combining sashimi scripts into release automation • Dependency testing • Stress • Performance • Install / Uninstall
- 25. Capstone Project 2017 25 Regression Testing • Subset (or all) can be executed nightly as CI build test • Integration of previous releases and sprints • Comprehensive, thorough verification • Identify “lost” fixes and new issues • Automated tests to expose bugs that were previously fixed – in case they return • Automated tests of new sprint functionality “Regression Stagger” – if needed
- 26. Capstone Project 2017 26 Continuous Feedback • Collaborates to share information • Daily stand-up for synchronization • Tracks bugs in tool, but communicates face-to-face for awareness • Ensures today’s efforts are in line with team priorities and goals • Supports the developers any way he/she can • “WE” instead of me – don’t point fingers
- 27. Capstone Project 2017 27 Agile: Team-Based Quality Software engineers • QA begins with developers! • Simple designs • Supports strong “definition of done” • Adhere to rigorous quality plan • Use TDD to manage technical debt • Use CI to find problems at earliest opportunity QA engineers • Additional quality verification • Supports strong “definition of done” • Verify all levels of code output - Sashimi - Integrated, incremental sashimi - Release/system - Regression • Automate, automate, automate
- 28. Common Mistakes
- 29. Capstone Project 2017 29 Common Mistakes • QA sashimi tests run in subsequent sprint - Violates “potentially shippable product increment” • Mini-waterfall handoff to QA within sprint - Violates lean/agile principles • Manual testing of sashimi slices - Latency of feedback - You won’t have time • QA not involved in user story development - Violates holistic team-based approach • QA not involved in release/sprint planning - Violates “committed team” principle • QA not physically located with project team - Violates “co-location” principle
- 30. Conclusion
- 31. Capstone Project 2017 31 Take-Aways • Agile – much more emphasis on QA than traditional approach • QA test specialist is an integral member of the development team • Being a QA tester is much more prestigious in Agile - Peer with software developers - Respect is shown through better communication & collaboration - Required involvement up-front and throughout! • Different role, different responsibilities, different skills • Agile – much better chance at delivering high-quality software on time
- 32. THANK YOU