An Introduction to Agile Testing Agile Tour Kaunas 2013
•Télécharger en tant que PPTX, PDF•
0 j'aime•876 vues
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (17)
Similaire à An Introduction to Agile Testing Agile Tour Kaunas 2013
Similaire à An Introduction to Agile Testing Agile Tour Kaunas 2013 (20)
Plus de Clement Pickering
Dernier
Dernier (20)
An Introduction to Agile Testing Agile Tour Kaunas 2013
- 1. An Introduction to Agile Testing The many shapes of modern testing Clement Pickering, Head of Testing, Callcredit September 2013
- 2. Testing is no longer a phase Quality is everyone’s responsibility Testing has become a highly skilled, exciting dynamic profession The shape of Testing is changing
- 3. It’s Just All Testing, Right? • Today’s aim – to introduce what agile testing is all about • How and Why it is different from traditional approaches • Key underlying principles • To share examples from Callcredit • Focus on three key angles … 1. People & Mindset 2. Strategy & Approach 3. Tools & Techniques • … and the many shapes of agile testing
- 4. Who are Callcredit? • Callcredit is a UK Credit Reference Agency, with key offices in Leeds and Kaunas • Callcredit has now formally adopted an Agile methodology, DSDM Atern • Various disparate Development areas now all together under one group function • Different backgrounds to QA – from no QA to waterfall QA
- 6. A is for Advocacy (NOT Assurance) Quality is not just testing NOT Testing is a rubberstamp
- 7. Testing is part of the Process (NOT a phase) Testing is part of the process NOT Testing phase gets squeezed
- 8. One Team Approach Collaboration, one team NOT Independent police
- 9. Generalising Specialists Flexible Team, generalising NOT specialists Functional silos, imposed job boundaries
- 10. Experts in Information One team recommendation NOT QA sign-off
- 11. •Removal of QA sign-off •Project team seating •Community of test practice not separate department •Integrated entryexit quality process •Constant, consistent message •Events on agile testing •Encouraging testers and developers to learn outside roles
- 13. Lightweight Visible Test Strategy
- 14. Infinite Test Cycles Change accommodated NOT Change expensive
- 15. Prevent not Find Prevent not find NOT Find, unable to prevent
- 16. Shapes on Testing #1 – Quadrants http://www.slideshare.net/ehendrickson/the-thinking-tester-evolved
- 17. Shapes on Testing #2 – Corners http://dannorth.net/
- 18. Shapes on Testing #3 – Coverage Blanket
- 19. •Test Strategy Posters •Prevent not fix – no logging of bugs found in Integration Environments •Test first Development •Team empowered to choose their approach and encouraged to think of testing and quality from many different angles
- 21. The Right Tool for the Right Job Toolbox of specialist tools NOT One tool fits all
- 22. Shapes on Testing #4 – Test Pyramid Exploratory Exploratory Selenium; QTP; WebDriver; Manual QC SoapUI; Internal tools; LoadRunner SpecFlow; Fitnesse; beHat xUnit UAT UI Service BDDATDD Unit
- 23. Automate and Integrate Continuous Integrated Testing NOT Single Test Cycle
- 24. •Testing pyramid – layers of testing •BDDATDD tools (SpecFlow, Fitnesse) •Service tools (SoapUI, Orion, WCFStorm) •Use of more environments •Continuous integration
- 25. Conclusions
- 26. • Modern Software Development requires a different approach to Testing • Agile Testing is more than just testing at the end of sprints, it’s a whole different mindset • Testing is no longer a manual low-skilled role – it’s challenging, technical, integrated and exciting • Changing the testing culture is key (but the hardest challenge) The Shape of Testing is Changing
Notes de l'éditeur
- Biggest challenge is to break down the traditional views on QA and testing
- Traditionally testers are powerless to influence quality only report on itQuality is a feature of the system, not a roleAssistance or Advocacy, not Assurance or AuditQuality is everyone’s responsibility
- Avoid the pattern of having testing at the end of timeboxes or a timebox behindResist developers setting off on new stuff
- Testers are not the policeTeam should work as one, everyone can testTeam takes pride in quality of the final product
- Cycling team analogyTesters shouldn’t be the only ones executing testsTesters can help the team learn about testing and quality and make sure testing is part of the process
- Testers are experts in finding out and providing informationTeam responsibility – make information visible and highlight risks and recommendations
- Dojos, lunchs, testing community events, webinars
- Testing is part of the processDifference between approaches agile vs traditional
- Visible documentation rather than un-read documentsPrompts conversationWindow into the testing and quality approaches of the teamLiving documentWhole team
- Notion of test cycles in obsolete – need to be able to repeat, repeat, repeatAutomation not a goal in itself but a means to an endContinuous Integration
- Defects can be harmful – as targetsThe best testers find no bugs as they’ve helped prevent themDefect management still needed – but more for a memory aid and significantly less important
- Assessing the risk of your project from different angles – have you covered them all?
- Another angle on risk and strategy – have you considered testing through this shape?Most tests lie along the forward slash angle, but the back slash angle is often overlooked
- Matching the shape of tests to the task at hand
- Practical aspects – tools for the job
- One tool does not fit allCode language analogy – css, javascript, .NET, SQL
- Layered approach to testingAutomate lower down, less brittle
- Need for automation to allow repeatitionFrees testers up for more interesting and value-adding rolesRequires more technical skills