Agile Testing: A Practical Guide for Testers and Agile Teams

Agile Testing: A Practical Guide for Testers and Agile Teams

Lisa Crispin, Janet Gregory

Language: English

Pages: 576

ISBN: 0321534468

Format: PDF / Kindle (mobi) / ePub

Te>Two of the industry’s most experienced agile testing practitioners and consultants, Lisa Crispin and Janet Gregory, have teamed up to bring you the definitive answers to these questions and many others. In Agile Testing, Crispin and Gregory define agile testing and illustrate the tester’s role with examples from real agile teams. They teach you how to use the agile testing quadrants to identify what testing is needed, who should do it, and what tools might help. The book chronicles an agile software development iteration from the viewpoint of a tester and explains the seven key success factors of agile testing.

Readers will come away from this book understanding

How to get testers engaged in agile development

Where testers and QA managers fit on an agile team

What to look for when hiring an agile tester

How to transition from a traditional cycle to agile development

How to complete testing activities in short iterations

How to use tests to successfully guide development

How to overcome barriers to test automation

This book is a must for agile testers, agile teams, their managers, and their customers.

The eBook edition of Agile Testing also is available as part of a two-eBook collection, The Agile Testing Collection (9780134190624).

quality—and if it’s not, we question whether it’s really an “agile” team. Your situation is unique. That’s why you need to be aware of the potential testing obstacles your team might face and how you can apply agile values and principles to overcome them. S UMMARY 17 S UMMARY Understanding the activities that testers perform on agile teams helps you show your own team the value that testers can add. Learning the core practices of agile testing will help your team deliver software that

wasn’t that I’d really end up thinking like a developer and just releasing anything, but that my manager, who was not a tester, wouldn’t care as much, and might not back up my concerns with the application. Ultimately, I think I ended up thinking slightly more like a developer, being less concerned about some of the small bugs. My better understanding of the application’s workings made me understand that the risk and cost of ﬁxing it was potentially much more risky than the beneﬁt. I believe that

approach, and focus of the software testing effort for stakeholders. The completed document is intended to help people outside the test group understand the “why” and “how” of product validation. In this section, we look at test plans and other aspects of preparing and tracking the testing effort for an agile project. Test Strategy vs. Test Planning In an agile project, teams don’t rely on heavy documentation to communicate what the testers need to do. Testers work hand in hand with the rest of

and Janet, people who dove right in alongside the programmers, testers who were not jealous of their role or their independence, downright pleasant people who could ﬁgure out the biggest change of all in Agile testing: the tester’s new social role. As a result, we have this book. It’s the stable solution, the good way for testers to live in this new Agile land of ours. It’s not the ﬁnal word—we could use the wheel, and I myself am eager for someone to invent antibiotics—but what’s taught here

development involves both test-ﬁrst programming and test-ﬁrst design, but there’s a subtle difference: “With test-ﬁrst design, the design follows the tests, whereas you can do test-ﬁrst programming of a design that you ﬁrst write down on a whiteboard. On larger projects, we tend to do more design via whiteboard discussions; the team discusses the architecture around a whiteboard, and codes test-ﬁrst based on this design. On smaller projects, we do practice test-driven design.” 114 C HAPTER 7