- Paperback: 160 pages
- Publisher: The Pragmatic Programmers; 1 edition (8 March 2013)
- Language: English
- ISBN-10: 1937785025
- ISBN-13: 978-1937785024
- Product Dimensions: 19 x 1.3 x 23.5 cm
- Boxed-product Weight: 363 g
- Customer Reviews: 31 customer ratings
- Amazon Bestsellers Rank: 158,220 in Books (See Top 100 in Books)
Other Sellers on Amazon
+ FREE Delivery
Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing Paperback – 8 March 2013
|New from||Used from|
Frequently bought together
Customers who bought this item also bought
""Reading this book taught me new skills and heuristics; but even better, it helped me channel my tester "spidey sense" more creatively and usefully. I keep this book handy at all times and occasionally do one of the practice sessions to keep my awareness keen. Explore It! helps me make sure our customers and our company get real value from our software. It'll help you too.""--Lisa Crispin, Coauthor with Janet Gregory, "Agile Testing: A Practical Guide for Testers and Agile Teams"""
""Explore It! starts with a bang. Elisabeth catches your imagination and has filled the book with practical ideas for exploring everything from your typical GUI scenarios to testing ideas (requirements), and she even includes suggestions for programmers on how to explore low-level code. This book should be on every development team member's desk, not only testers. It is the book I carry with me whenever I introduce exploratory testing to development teams.""--Janet Gregory, Coauthor with Lisa Crispin, "Agile Testing: A Practical Guide for Testers and Agile Teams"
About the Author
Elisabeth Hendrickson is a tester, developer, and Agile enabler. A seasoned veteran, she wrote her first line of code in 1980, and almost immediately found her first bug. In 2010 she won the prestigious Gordon Pask Award from the Agile Alliance. She is best known for her Google Tech Talk on Agile Testing as well as her wildly popular Test Heuristics Cheatsheet. She splits her time between teaching, speaking, writing, programming, and working on Agile teams that value her obsession with testing.
Customers who viewed this item also viewed
|5 star 76% (76%)||76%|
|4 star 12% (12%)||12%|
|3 star 13% (13%)||13%|
|2 star 0% (0%)||0%|
|1 star 0% (0%)||0%|
Review this product
Top international reviews
The last few chapters will be most useful to anyone who is new to testing and struggled to frame the patterns and techniques in the book into their current day job. Trust me, everything you hear other people in completely different industries doing in their unrelated testing fields is in fact relevant to you, you just need to grasp the context, something this book does take the time to do. A lean tome, but easy to digest.
It also only gets into how important it is to collaborate with developers and other stakeholders very late in the book. Things like "exploring what happens if a config file is unavailable" could be discovered most easily by speaking to the developer instead of setting up an elaborate test and if the tester hasn't got access to developers then that needs resolving.
Having said that, it does offer good advise and insight into identifying what may be missing or ambiguous in the requirements and to a large degree it is only possible to discover a lot of those things after creating working versions of the software.
My only worry is that once reading this book, testers at typical employers will become disenchanted. Most organisations have such a poor attitude to testing that they are still manually running the regression tests that should have been automated (quadrant 2 in the Agile Testing Quadrants), and consequently never have time for scheduled exploratory testing. Maybe this book can contribute to turning those organisations around. I hope so.
In my years of working in software development I have noticed to paths testers take. Chaotic, where they initially try to break the system with the most extreme choices they can, and spec testers that work closely to specific test cases. If a person applies the principles in this book to software testing it will lead to respectable feedback to the developers for addressing deficiencies (whether those are bugs or expected functionality that is lacking). The benefits of both the harsh and spec based testing will be made manifests in exploratory testing.
The chapter on chartering is excellent, because it not only proposes a good practice for software testing but for addressing a multitude of problems. It is as follows: Explore ___ with ___ to discover ____. Outside of testing software consider its application to acquiring virtues, trying out new team practices, or making any type of major "trial" to see if a process is in somehow improved.
The Test Heuristics cheat sheet is excellent for beginners, and is worth going over with your newer software testers so that they are providing value above that of just a standard user testing the software.
I would recommend this book and encourage members of my team to read it.