Adapt your tes-ng approach for Agile Emma Armstrong @EmmaATester www.taoo;es-ng.,co,uk Emma.armstrong@towerswatson.com
Today s Session So;ware development methodologies Tes-ng in those methodologies Agile methodologies Tes-ng within Agile Iden-fying the tes-ng challenges in agile Iden-fying ways to overcome those challenges
So.ware Development Methodologies Tradi-onal methodologies Waterfall and V model methodologies Prototyping Incremental, spiral, Rapid applica-on development Incremental Itera-ve and Incremental Spiral Rapid applica-on development Agile Kanban, Scrum Code and Fix
Exercise One You have all just become developers Grab a piece of paper and a pen You now have 5 minutes to draw a house So now for some tes-ng
Development Lifecycle - Waterfall Planning Analysis Design Coding Tes-ng
TesBng Pyramid UI System Integra-on Unit
Test Techniques Parafunc-onal Func-onal Usability Security Installa-on regression Equivalence class BVA
Development Lifecycle - IteraBve Planning Release Analysis Tes-ng Design Coding
Exercise Two Get into groups of three Each grab a piece of paper and a pen Decide who is the developer, who is the product owner and who is the tester. You now have 10 minutes to draw a car/vehicle
What is Agile? Manifesto for Agile So0ware Development We are uncovering bewer ways of developing so;ware by doing it and helping others do it. Through this work we have come to value: Individuals and interac-ons over processes and tools Working so;ware over comprehensive documenta-on Customer collabora-on over contract nego-a-on Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the le; more.
Aim of Agile Adap-ve planning Evolu-onary development Early delivery Con-nuous improvement Rapid/flexible response to change
Development cycle - Agile Done In Progress Backlog
TesBng on Agile Product Managers Idea Story Creation Sprint Planning Feature Implemented Feature Complete Release Sprint Review Sprint Retro Story Development Bug Fixing Release Cycle Red Route Testing Exploratory Phase Retesting Story verification Define test approach Identify related based on test known bugs strategy Define test plan Validation AC Agreement Planning & Prep Story Task Collaborate breakdown identification outside & inside Review plan (rubber duck) User scenario/ sanity path Testing Go live Merge Retest Housekeeping Document Tidy-up Testing Review Identify skills gap Identify environments Code Tests Docs Clean install consider blogging/email lightning talk Identify risks Division of responsibility Links/redirects Upgrade Left over tasks Identify key risks Throughout the sprint... Licensing Automate Red route test cases Re-assess Note any ideas & issues Learn for next time Identify techniques From Chris George and Emma Armstrong
From Lisa Crispin and Janet Gregory
Adapt our TesBng Go beyond tes-ng Different test approaches TDD, BDD, ATDD, Con-nuous integra-on/delivery Ini-ate Change Kaizen approach Communica-on even more
Learn more Exploratory Tes-ng Explore it by Elisabeth Hendrickson Session based tes-ng Rapid so;ware Tes-ng James Bach Lean Tes-ng MaW Heusser
QuesBons?
Adapt your tes-ng approach for Agile Emma Armstrong @EmmaATester www.taoo;es-ng.,co,uk Emma.armstrong@towerswatson.com