Explore It!: Reduce Risk and Increase Confidence with Exploratory Testing 1st Edition, Kindle Edition
Use the Amazon App to scan ISBNs and compare prices.
Software is full of surprises. No matter how careful or skilled you are, when you create software it can behave differently than you intended. Exploratory testing mitigates those risks.
Part 1 introduces the core, essential skills of a master explorer. You’ll learn to craft charters to guide your exploration, to observe what’s really happening (hint: it’s harder than it sounds), to identify interesting variations, and to determine what expected behavior should be when exercising software in unexpected ways.
Part 2 builds on that foundation. You’ll learn how to explore by varying interactions, sequences, data, timing, and configurations. Along the way you’ll see how to incorporate analysis techniques like state modeling, data modeling, and defining context diagrams into your explorer’s arsenal.
Part 3 brings the techniques back into the context of a software project. You’ll apply the skills and techniques in a variety of contexts and integrate exploration into the development cycle from the very beginning.
You can apply the techniques in this book to any kind of software. Whether you work on embedded systems, Web applications, desktop applications, APIs, or something else, you’ll find this book contains a wealth of concrete and practical advice about exploring your software to discover its capabilities, limitations, and risks.
Inspire a love of reading with Amazon Book Box for Kids
Discover delightful children's books with Amazon Book Box, a subscription that delivers new books every 1, 2, or 3 months — new Amazon Book Box Prime customers receive 15% off your first box. Sign up now
From the brand
""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"--This text refers to the paperback edition.
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.--This text refers to the paperback edition.
- ASIN : B00I8W50T8
- Publisher : Pragmatic Bookshelf; 1st edition (February 21, 2013)
- Publication date : February 21, 2013
- Language : English
- File size : 1093 KB
- Simultaneous device usage : Unlimited
- Text-to-Speech : Enabled
- Screen Reader : Supported
- Enhanced typesetting : Enabled
- X-Ray : Not Enabled
- Word Wise : Not Enabled
- Print length : 211 pages
- Lending : Not Enabled
- Best Sellers Rank: #439,822 in Kindle Store (See Top 100 in Kindle Store)
- Customer Reviews:
About the author
Top reviews from the United States
There was a problem filtering reviews right now. Please try again later.
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.
The book is easy to read and each chapters is meaningful on it's own.
In my opinion it is a must read for anyone who works with software development no matter if you are a tester, programmer, scrum master, manager, etc...
Short and to the point. No fluff, just useful methods of exploratory testing. Other testing books require you not only to change your testing habits, but also how others work. This is not always realistic.
This book is about helping the reader become better at testing. It's a personal adventure.
Top reviews from other countries
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.