Most ebook files are in PDF format, so you can easily read them using various software such as Foxit Reader or directly on the Google Chrome browser.
Some ebook files are released by publishers in other formats such as .awz, .mobi, .epub, .fb2, etc. You may need to install specific software to read these formats on mobile/PC, such as Calibre.
Please read the tutorial at this link. https://ebooknice.com/page/post?id=faq
We offer FREE conversion to the popular formats you request; however, this may take some time. Therefore, right after payment, please email us, and we will try to provide the service as quickly as possible.
For some exceptional file formats or broken links (if any), please refrain from opening any disputes. Instead, email us first, and we will try to assist within a maximum of 6 hours.
EbookNice Team
Status:
Available5.0
24 reviewsISBN 10: 0321636414
ISBN 13: 9780321636416
Author: James A Whittaker
How to Find and Fix the Killer Software Bugs that Evade Conventional Testing In Exploratory Software Testing, renowned software testing expert James Whittaker reveals the real causes of today’s most serious, well-hidden software bugs--and introduces powerful new “exploratory” techniques for finding and correcting them. Drawing on nearly two decades of experience working at the cutting edge of testing with Google, Microsoft, and other top software organizations, Whittaker introduces innovative new processes for manual testing that are repeatable, prescriptive, teachable, and extremely effective. Whittaker defines both in-the-small techniques for individual testers and in-the-large techniques to supercharge test teams. He also introduces a hybrid strategy for injecting exploratory concepts into traditional scripted testing. You’ll learn when to use each, and how to use them all successfully. Concise, entertaining, and actionable, this book introduces robust techniques that have been used extensively by real testers on shipping software, illuminating their actual experiences with these techniques, and the results they’ve achieved. Writing for testers, QA specialists, developers, program managers, and architects alike, Whittaker answers crucial questions such as: • Why do some bugs remain invisible to automated testing--and how can I uncover them? • What techniques will help me consistently discover and eliminate “show stopper” bugs? • How do I make manual testing more effective--and less boring and unpleasant? • What’s the most effective high-level test strategy for each project? • Which inputs should I test when I can’t test them all? • Which test cases will provide the best feature coverage? • How can I get better results by combining exploratory testing with traditional script or scenario-based testing? • How do I reflect feedback from the development process, such as code changes?
Chapter 1 The Case for Software Quality
The Magic of Software
The Failure of Software
Conclusion
Exercises
Chapter 2 The Case for Manual Testing
The Origin of Software Bugs
Preventing and Detecting Bugs
Preventing Bugs
Detecting Bugs
Manual Testing
Scripted Manual Testing
Exploratory Testing
Conclusion
Exercises
Chapter 3 Exploratory Testing in the Small
So You Want to Test Software?
Testing Is About Varying Things
User Input
What You Need to Know About User Input
How to Test User Input
State
What You Need to Know About Software State
How to Test Software State
Code Paths
User Data
Environment
Conclusion
Exercises
Chapter 4 Exploratory Testing in the Large
Exploring Software
The Tourist Metaphor
“Touring” Tests
Tours of the Business District
Tours Through the Historical District
Tours Through the Entertainment District
Tours Through the Tourist District
Tours Through the Hotel District
Tours Through the Seedy District
Putting the Tours to Use
Conclusion
Exercises
Chapter 5 Hybrid Exploratory Testing Techniques
Scenarios and Exploration
Applying Scenario-Based Exploratory Testing
Introducing Variation Through Scenario Operators
Inserting Steps
Removing Steps
Replacing Steps
Repeating Steps
Data Substitution
Environment Substitution
Introducing Variation Through Tours
The Money Tour
The Landmark Tour
The Intellectual Tour
Chapter 6 Exploratory Testing in Practice
The Touring Test
Touring the Dynamics AX Client
Useful Tours for Exploration
The Collector’s Tour and Bugs as Souvenirs
Tour Tips
Using Tours to Find Bugs
Testing a Test Case Management Solution
The Rained-Out Tour
The Saboteur
The FedEx Tour
The TOGOF Tour
The Practice of Tours in Windows Mobile Devices
My Approach/Philosophy to Testing
Interesting Bugs Found Using Tours
Chapter 7 Touring and Testing’s Primary Pain Points
The Five Pain Points of Software Testing
Aimlessness
Define What Needs to Be Tested
Determine When to Test
Determine How to Test
Repetitiveness
Know What Testing Has Already Occurred
Understand When to Inject Variation
Transiency
Monotony
Memorylessness
Conclusion
Exercises
Chapter 8 The Future of Software Testing
Welcome to the Future
The Heads-Up Display for Testers
“Testipedia”
Test Case Reuse
Test Atoms and Test Molecules
Virtualization of Test Assets
Visualization
Testing in the Future
exploratory software testing book
exploratory software
examples of exploratory testing
exploratory usability testing
exploratory data analysis with r roger peng
Tags: James A Whittaker, Exploratory, Software