- Paperback: 576 pages
- Publisher: Addison-Wesley Professional; 1 edition (January 9, 2009)
- Language: English
- ISBN-10: 0321534468
- ISBN-13: 978-0321534460
- Product Dimensions: 7 x 1.2 x 9 inches
- Shipping Weight: 2 pounds (View shipping rates and policies)
- Average Customer Review: 65 customer reviews
- Amazon Best Sellers Rank: #231,656 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Agile Testing: A Practical Guide for Testers and Agile Teams 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Author interviews, book reviews, editors picks, and more. Read it now
Frequently bought together
Customers who bought this item also bought
“As Agile methods have entered the mainstream, we’ve learned a lot about how the testing discipline fits into Agile projects. Lisa and Janet give us a solid look at what to do, and what to avoid, in Agile testing.”
–Ron Jeffries, www.XProgramming.com
“An excellent introduction to agile and how it affects the software test community!”
–Gerard Meszaros, Agile Practice Lead and Chief Test Strategist at Solution Frameworks, Inc., an agile coaching and lean software development consultancy
“In sports and music, people know the importance of practicing technique until it becomes a part of the way they do things. This book is about some of the most fundamental techniques in software development–how to build quality into code–techniques that should become second nature to every development team. The book provides both broad and in-depth coverage of how to move testing to the front of the development process, along with a liberal sprinkling of real-life examples that bring the book to life.”
–Mary Poppendieck, Author of Lean Software Development and Implementing Lean Software Development
“Refreshingly pragmatic. Chock-full of wisdom. Absent of dogma. This book is a gamechanger. Every software professional should read it.”
–Uncle Bob Martin, Object Mentor, Inc.
“With Agile Testing, Lisa and Janet have used their holistic sensibility of testing to describe a culture shift for testers and teams willing to elevate their test effectiveness. The combination of real-life project experiences and specific techniques provide an excellent way to learn and adapt to continually changing project needs.”
–Adam Geras, M.Sc. Developer-Tester, Ideaca Knowledge Services
“On Agile projects, everyone seems to ask, ‘But, what about testing?’ Is it the development team’s responsibility entirely, the testing team, or a collaborative effort between developers and testers? Or, ‘How much testing should we automate?’ Lisa and Janet have written a book that finally answers these types of questions and more! Whether you’re a tester, developer, or manager, you’ll learn many great examples and stories from the real-world work experiences they’ve shared in this excellent book.”
–Paul Duvall, CTO of Stelligent and co-author of Continuous Integration: Improving Software Quality and Reducing Risk
“Finally a book for testers on Agile teams that acknowledges there is not just one right way! Agile Testing provides comprehensive coverage of the issues testers face when they move to Agile: from tools and metrics to roles and process. Illustrated with numerous stories and examples from many contributors, it gives a clear picture of what successful Agile testers are doing today.”
–Bret Pettichord, Chief Technical Officer of WatirCraft and Lead Developer of Watir
From the Back Cover
Testing is a key component of agile development. The widespread adoption of agile methods has brought the need for effective testing into the limelight, and agile projects have transformed the role of testers. Much of a tester's function, however, remains largely misunderstood. What is the true role of a tester? Do agile teams actually need members with QA backgrounds? What does it really mean to be an "agile tester?"
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
Top customer reviews
I say that because the usefulness of this book has a lot to do with your organization, and what your starting point is. If you are working on a development team starting from scratch then this is a must read for any lead or manager involved. There is a ton of high level conceptual information in here that will help you draw out an outline of what you need to think about in terms of testing over the next few months. This runs from what broad categories needs to be tested (Security, -ility, GUI, etc.) to who is responsible for automation (Unit test, API testing, etc.). I can honestly say that sticking to these concepts will help you make a better product faster.
Here's the downside. If you are coming in midway through a project then get ready for the battle of a lifetime getting this stuff implemented no matter how much sense it makes. Unit testing, as an example, is constantly brought up throughout the book, and that is not something that you can get up and going with a snap of your fingers. Especially if you have to educate development on how to do it. This book provides little support in that sort of area, and, honestly, that is most likely the scenario that most people in QA will run into. I have been in QA for ten years, and every place I have worked either had no unit testing at all or the had just enough to claim that they did.
The reality is that Agile Testing in this book equates to Test Driven Development with QA support. That mean QA is responsible for a lot of solution, end to end, and customer requirement verification testing, but very little feature and functionality testing since that is expected to be done in unit testing. If you are in QA and you need to read this book then you almost certainly do no have that already, and need a book that tells you how to do it.
So, anyways, this book is worth reading if you are just starting out, but make sure you are reading it with development and project management as well. If you are not just starting out then In my opinion these steps are required:
1. Get acceptance from Management, Dev, and Project Management that your current model is not sustainable, and that resources will be allocated to changing that.
2. Read this book with all of those involved.
3. Meet up and list out what the book recommends, where you are strong, and where you are weak.
4. Use that as a starting point to find other books and resources to strengthen up your weak points.
5. Make sure that management makes the success of these changes part of everyone's job responsibility, and emphasizes it as part of performance evaluations. Period.
In my experience, if you can't get the five steps above completed then you might as well throw this book out the window, because you'll waste a bunch of time implementing QA practices that will fail miserably due to their reliance on a non existant foundation. Step five is the real key. Otherwise you get one of the following:
1. "Great Idea!" with no action following
2. "You're right, we need these changes," and then an expectation that QA will be responsible for all of them. Including things like forcing individual dev's to do unit testing.
The weakness in the book is that it doesn't really address the needs of QA in terms of helping you get through those five steps.
If you use this book as a planning tool then you will be in good shape and the value is absolutely there. It is a quick and easy read, gets the concepts across in a way that pretty much anyone can understand, and does so convincingly. Just don't go in expecting it to answer all your problems without some supplemental reading. You will need to read up on automation and unit testing frameworks and test driven development.
Before they get to that point, they help readers understand common organizational issues that hinder the transition to agile. They elaborate on the implications of the Agile Manifesto to how individuals, teams, and organizations operate. It is not ivory tower wisdom from above either, but it is rather hard fought, experienced based observations that will help novices avoid some of the potential growing pains. In addition, they give a solid taxonomy of test covering functional and non-functional. They address what types of testing to automate and when. Finally, they spend two chapters in detail on automation strategy and implementation. At regular intervals, readers see either "Lisa's Story" or "Janet's Story" that details with the concept being discussed. These either tell what worked well or how they overcame specific challenges.
I found Crispin and Gregory had a very accessible writing style, and they do a great job of getting their point across. If you are a traditional tester who is unsure or even afraid of moving into the agile world, this is the book that you need. They tackle the tough questions that most people have one by one with answers that can be put in practice. I plan to use the wisdom of this book in helping my testing organization make the transition. I highly recommend this book.
Book that deserves reading is Software Testing by Ron Patton, purchased it as well and very happy, it is really good.