Uncover surprises, risks, and potentially serious bugs with exploratory testing. Rather than designing all tests in advance, explorers design and execute small, rapid experiments, using what they learned from the last little experiment to inform the next. Learn essential skills of a master explorer, including how to analyze software to discover key points of vulnerability, how to design experiments on the fly, how to hone your observation skills, and how to focus your efforts. 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.

Reduce Risk and Increase Confidence with Exploratory Testing

Explore It!

Explore-Increase-Confidence-Exploratory-Testing

To build high-quality software, you need to write testable code. That's harder than it seems: It requires insights drawn from arenas ranging from software craftsmanship to unit testing, refactoring to test-driven development. Most programming books either discuss testing only briefly, or drill down on just one or two techniques, with little guidance on how to systematically verify code. Most testing books, on the other hand, focus on a specific testing process, without showing how to write software that can be easily and systematically tested. In " Developer Testing, " leading software engineering consultant Alexander Tarlinder strikes an optimal balance, integrating insights from multiple disciplines to help frustrated practitioners get better results. Drawing on his extensive experience as a mentor and trainer, he offers insights that help you accelerate through the typical software assurance learning curve, so you can progress far more rapidly. Tarlinder organizes his insights into "chunks" to help you quickly absorb key concepts, and focuses on technology-agnostic approaches you can keep using with any new language, platform, or toolset. Along the way, he answers many questions development teams often ask about testing, including: What makes code testable? What makes it hard to test? When have I done enough testing on a piece of code? How many unit tests do I need to write? Exactly what should my test verify? How do I transform monolithic legacy code into manageable pieces I can test? What's the best way to structure my tests? The first guide to cover testing mindset, techniques, and applications from the developer's perspective, "Developer Testing" will help developers get what they really want: better code."

devtobook

Explore It!2

紹介された本（洋書）

Explore It!

Reduce Risk and Increase Confidence with Exploratory Testing

日本語版（翻訳本）

Developer Testing1

紹介された本（洋書）

Developer Testing

Building Quality Into Software

日本語版（翻訳本）