Seven Deadly Sins of Agile Testing

Size: px

Start display at page:

Download "Seven Deadly Sins of Agile Testing"

Baldwin Hampton
5 years ago
Views:

1 Seven Deadly Sins of Agile Testing

2 2 About me Brad Swanson

3 Time to market Traditional Development Analyze Implement Test Agile Development Deliverable Deliverable 3

4 Risk Risk traditional agile Time 4

5 Schedule Confidence? 5

6 6 Productivity

7 + Early to market advantage ROI $ - agile traditional time 7

8 Quality traditional Open defects agile Time 8

9 9 Source: Dr. Dobb s Journal 2008 Agile Adoption Survey

10 Sin #7: Separation of Requirements & Tests Req Spec Tests 10

11 Penance Create an executable specification: Spec == Tests Use concrete examples to specify requierements Analysts and Testers become best friends! Acceptance Test Driven Development (ATDD, BDD) Cucumber, FIT, Fitnesse, Selenium Other tools??? INVEST in user stories Independent, Negotiable, Valuable, Estimable, Small, Testable Include testing in the Definition of Done for stories & sprints Expand your skills 11

12 Sin #6: Testing is one sprint behind Code sprint 1 Code sprint 2 Code sprint 3 Code sprint 4 Test Sprint 1 Test Sprint 2 Test Sprint 3 Test Sprint 4 12

13 Penance Include testing in the Definition of Done for stories & sprints Smaller backlog items & user stories Testers define & create tests at the start of each story/sprint Automated testing / TDD / ATDD / BDD 13

14 14 Sin #5: Unbalanced Testing Quadrants

15 Penance Include the appropriate testing quadrants in the Definition of Done for stories, sprints, and releases. Have a balanced testing plan as part of release planning Create backlog items for appropriate testing activities, e.g. ility testing. Get management commitment to support effort needed to catch up on test automation; show the ROI on automation. Get real users & stakeholders to participate in acceptance testing early and often. 15

16 16 Sin #4: Ignoring Test Failures

17 17

18 Penance Discipline: stop the line whenever the CI build & tests fail Invest in making automated tests robust Create incentives for team members to have clean check-ins; friendly competition? Take metrics: reward people for improving quality and automated test coverage 18

19 19 Sin #3: Lack of TDD & CI

20 Penance Commit as a team to doing TDD and CI Discipline: keep it going Expand your skills Invest in infrastructure, tools, training. Show the ROI. Keep metrics to measure resulting quality improvements 20

21 Sin #2: Separate QA Team Dev Dev Dev Dev QA QA QA QA Dev Dev QA QA 22

22 Penance Form cross-functional teams including QA Co-located teams: same room Do a pilot project with QA dedicated to the team; keep metrics to demonstrate the results. Keep QA fully involved with the team: planning, implementing stories, demos, retrospectives Whole-team responsibility for product quality 23

23 Sin #1: WaterScrumming Analysis sprint Analysis sprint Code sprint Code sprint Code sprint Test sprint Test sprint Test sprint 24

24 Penance Form cross-functional teams including QA & analysts Include testing in the Definition of Done for stories & sprints INVEST in user stories Independent, Negotiable, Valuable, Estimable, Small, Testable Testers define & create tests at the start of each story/sprint TDD / ATDD / BDD Allow one hardening sprint before release with all hands on deck testing 25

25 26

26 27

27 License agreement At least part of the material used in this presentation has been licensed as Creative Common, non-commercial, sharealike content ( from agile42 GmbH. As per the license agreement you are entitled to do whatever you like to the material as far as is not contradicting basic principle of the license. On top of that agile42 GmbH kindly asks you to return any change you will make to this material, for validation and sharing purposes.

BEHAVIOR DRIVEN DEVELOPMENT BDD GUIDE TO AGILE PRACTICES. Director, Strategic Solutions

BEHAVIOR DRIVEN DEVELOPMENT BDD GUIDE TO AGILE PRACTICES Presenter: Joshua Eastman Director, Strategic Solutions ABOUT THE SPEAKER Josh has over seven years of experience as an accomplished software testing