Agile Testing: A Practical Guide for Testers and Agile Teams,   ISBN:9780321534460

Customer Rating: 

I picked up this book as a recommendation from a coworker. I currently work on large team which is spread over 3 geographic locations. We are in the process of switching to agile, it's only our second release using/trying agile. This book answered a lot of questions I had about where and how QA/Testers would fit with in an agile environment.

Customer Rating: 

Lisa and Janet give us a path from testing specifications to testing in an Agile environment. In doing so, they have opened a new view on the importance and value that test provides Agile. Any one looking to take this journey is well advised to pack a copy of this book as it is a map to new ways of thinking about Agile, test, and value.

Customer Rating: 

Agile testing is a great book to both new and seasoned test engineers and test managers. At 533 pages, the book might feel a bit heavy but it is actually a pretty light and practical read if you read it to get a solid foundation on agile testing and then as reference. Note that the book is not about test coding techniques.

Part I is an introduction to agile testing and proposes ten principles for agile testers. What I don't know is if there are really 10 principles or if Crispin and Gregory forced it to be that specific number because it sounds better than 9 or 11. In any case, this chapter is a must read for all. Part II discusses organizational challenges, specifically cultural, logistical, and transitional from typical processes. This is a must-read for managers and team leads, and highly advisable for engineers if you want to have a successful test organization fully integrated with an agile organization. I personally encourage the division between development and testing to disappear completely. Part III is about he testing quadrants proposed by Brian Marick (one of the Agile Manifesto signatories) a while back. This is the first time I see the quadrants treated in larger detail and highly recommend it as a must for all.

Part IV is about test automation. It is a good read to understand the advantages of test automation and proposes a test automation strategy. This is a good starting point for test organizations that are new to automation but for mature test automation organizations it might add little value. Test code writing techniques are beyond the scope of this book. Part V illustrates the previous parts and then some by following a tester's activities through an agile iteration and the activities prior to it.

One problem I see way too often in test organizations and the way companies treat their test organizations is due to a lack of understanding not only of the difference between Quality Assurance and testing but also because of the place testing has hi people's minds. This book is a big help to create a cultural shift for the better.

Customer Rating: 

Almost all of the material in this book is just a review of standard agile practices. If you are new to agile then it gives a good overview and will serve as a good guide. Otherwise it doesn't bring any new insight.

Customer Rating: 

This book is a very interesting and easy read book. Don't miss it!!you would find what you were looking from the experienced people.