PDF Ebook Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker
The presented book Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker we provide right here is not type of normal book. You recognize, checking out now does not indicate to handle the printed book Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker in your hand. You can get the soft file of Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker in your gadget. Well, we mean that the book that we extend is the soft file of guide Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker The material and all points are exact same. The difference is only the types of guide Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker, whereas, this problem will exactly be profitable.
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker
PDF Ebook Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker
Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker. Thanks for visiting the very best internet site that supply hundreds sort of book collections. Right here, we will offer all books Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker that you need. The books from renowned authors and also publishers are given. So, you could appreciate currently to get individually sort of book Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker that you will look. Well, pertaining to the book that you want, is this Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker your option?
If you ally need such a referred Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker publication that will give you worth, obtain the very best seller from us now from several preferred authors. If you intend to entertaining publications, numerous stories, tale, jokes, and much more fictions compilations are likewise released, from best seller to one of the most recent launched. You might not be perplexed to appreciate all book collections Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker that we will certainly offer. It is not regarding the rates. It's about what you require now. This Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker, as one of the very best vendors below will be among the best selections to review.
Discovering the ideal Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker publication as the right need is sort of good lucks to have. To start your day or to end your day at night, this Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker will appertain sufficient. You could merely look for the floor tile right here as well as you will get the book Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker referred. It will not trouble you to reduce your important time to go for buying publication in store. In this way, you will certainly also spend cash to pay for transport and various other time spent.
By downloading and install the on-line Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker book here, you will certainly get some advantages not to opt for the book store. Simply hook up to the web and also begin to download and install the page web link we discuss. Currently, your Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By James A. Whittaker prepares to enjoy reading. This is your time as well as your tranquility to get all that you want from this publication Exploratory Software Testing: Tips, Tricks, Tours, And Techniques To Guide Test Design, By 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?
�
- Sales Rank: #925560 in Books
- Published on: 2009-09-04
- Original language: English
- Number of items: 1
- Dimensions: 9.10" h x .70" w x 7.00" l, .93 pounds
- Binding: Paperback
- 256 pages
From the Back Cover
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?
About the Author
James Whittaker has spent his career in software testing and has left his mark on many aspects of the discipline. He was a pioneer in the field of model-based testing, where his Ph.D. dissertation from the University of Tennessee stands as a standard reference on the subject. His work in fault injection produced the highly acclaimed runtime fault injection tool Holodeck, and he was an early thought leader in security and penetration testing. He is also well regarded as a teacher and presenter, and has won numerous best paper and best presentation awards at international conferences. While a professor at Florida Tech, his teaching of software testing attracted dozens of sponsors from both industry and world governments, and his students were highly sought after for their depth of technical knowledge in testing.
�
Dr. Whittaker is the author of How to Break Software and its series follow- ups How to Break Software Security (with Hugh Thompson) and How to Break Web Software (with Mike Andrews). After ten years as a professor, he joined Microsoft in 2006 and left in 2009 to join Google as the Director of Test Engineering for the Kirkland and Seattle offices. He lives in Woodinville, Washington, and is working toward a day when software just works.
�
Excerpt. � Reprinted by permission. All rights reserved.
Exploratory Software Testing Exploratory Software Testing Preface
“Customers buy features and tolerate bugs.”
—Scott Wadsworth
Anyone who has ever used a computer understands that software fails. From the very first program to the most recent modern application, software has never been perfect.
Nor is it ever likely to be. Not only is software development insanely complex and the humans who perform it characteristically error prone, the constant flux in hardware, operating systems, runtime environments, drivers, platforms, databases, and so forth converges to make the task of software development one of humankind’s most amazing accomplishments.
But amazing isn’t enough, as Chapter 1, “The Case for Software Quality,” points out, the world needs it to be high quality, too.
Clearly, quality is not an exclusive concern of software testers. Software needs to be built the right way, with reliability, security, performance, and so forth part of the design of the system rather than a late-cycle afterthought. However, testers are on the front lines when it comes to understanding the nature of software bugs. There is little hope of a broad-based solution to software quality without testers being at the forefront of the insights, techniques, and mitigations that will make such a possibility into a reality.
There are many ways to talk about software quality and many interested audiences. This book is written for software testers and is about a specific class of bugs that I believe are more important than any other: bugs that evade all means of detection and end up in a released product.
Any company that produces software ships bugs. Why did those bugs get written? Why weren’t they found in code reviews, unit testing, static analysis, or other developer-oriented activity? Why didn’t the test automation find them? What was it about those bugs that allowed them to avoid manual testing?
What is the best way to find bugs that ship?
It is this last question that this book addresses. In Chapter 2, “The Case for Manual Testing,” I make the point that because users find these bugs while using the software, testing must also use the software to find them. For automation, unit testing, and so forth, these bugs are simply inaccessible. Automate all you want, these bugs will defy you and resurface to plague your users.
The problem is that much of the modern practice of manual testing is aimless, ad hoc, and repetitive. Downright boring, some might add. This book seeks to add guidance, technique, and organization to the process of manual testing.
In Chapter 3, “Exploratory Testing in the Small,” guidance is given to testers for the small, tactical decisions they must make with nearly every test case. They must decide which input values to apply to a specific input field or which data to provide in a file that an application consumes. Many such small decisions must be made while testing, and without guidance such decisions often go unanalyzed and are suboptimal. Is the integer 4 better than the integer 400 when you have to enter a number into a text box? Do I apply a string of length 32 or 256? There are indeed reasons to select one over the other, depending on the context of the software that will process that input. Given that testers make hundreds of such small decisions every day, good guidance is crucial.
In Chapter 4, “Exploratory Testing in the Large,” guidance is given for broader, strategic concerns of test plan development and test design. These techniques are based on a concept of tours, generalized testing advice that guides testers through the paths of an application like a tour guide leads a tourist through the landmarks of a big city. Exploration does not have to be random or ad hoc, and this book documents what many Microsoft and Google testers now use on a daily basis. Tours such as the landmark tour and the intellectual’s tour are part of the standard vocabulary of our manual testers. Certainly, test techniques have been called “tours” before, but the treatment of the entire tourist metaphor for software testing and the large-scale application of the metaphor to test real shipping applications makes its first appearance in this book.
Testing in the large also means guidance to create entire test strategies. For example, how do we create a set of test cases that give good feature coverage? How do we decide whether to include multiple feature usage in a single test case? How do we create an entire suite of test cases that makes the software work as hard as possible and thus find as many important bugs as possible? These are overarching issues of test case design and test suite quality that have to be addressed.
In Chapter 5, “Hybrid Exploratory Testing Techniques,” the concept of tours is taken a step further by combining exploratory testing with traditional script or scenario-based testing. We discuss ways to modified end-to-end scenarios, test scripts, or user stories to inject variation and increase the bug-finding potential of traditionally static testing techniques.
In Chapter 6, “Exploratory Testing in Practice,” five guest writers from various product groups at Microsoft provide their experience reports from the touring techniques. These authors and their teams applied the tours to real software in real shipping situations and document how they used the tours, modified the tours, and even created their own. This is the first-hand account of real testers who ship important, mission-critical software.
Finally, I end the book with two chapters aimed at wrapping up the information from earlier chapters. In Chapter 7, “Touring and Testing’s Primary Pain Points,” I describe what I see as the hardest problems in testing and how purposeful exploratory testing fits into the broader solutions. In Chapter 8, “The Future of Software Testing,” I look further ahead and talk about how technologies such as virtualization, visualization, and even video games will change the face of testing over the next few years. The appendixes include my take on having a successful testing career and assemble some of my more popular past writings (with new annotations added), some of which are no longer available in any other form.
I hope you enjoy reading this book as much as I enjoyed writing it.
� Copyright Pearson Education. All rights reserved.
Most helpful customer reviews
3 of 3 people found the following review helpful.
some useful ideas, but lots of fluff, and bad editing
By Todd Bradley
I've read about 70% of the book and I think its usefulness is winding down for me. I disagree with the reviewer that said everything here is for entry level QA staff. I've been doing software engineering (development and test engineering) for about 24 years now (about 7 years of that as an agile tester) and a lot of this book is new to me. The real value here for me is the material on the tourist metaphor of testing, or what Whittaker and others call "touring tests" (pun intended). These are essentially "styles" of tests that any experienced test engineer has used in the past. But what's new is the focus on testing a product through these tours.
Most software organizations split up testing responsibilities in a way where one test engineer is assigned a feature, and then he tests that feature from a lot of different angles - acceptance tests, error tests, stress tests, etc. Whittaker's approach, as espoused in this book, is to turn things 90 degrees around. Instead of the classic way, give a test engineer one angle and then have him test all features from that angle. This exercises connections between features, which is where more bugs (supposedly) live.
That's the thesis, and most of rest of the good part of the book is material to help explain that and flesh it out. Unfortunately, there's also a lot of material that's just filler, like poorly-written blog articles from Whittaker's coworkers. A lot of the rest of it sounds like his own blog posts, too, and one whole appendix is literally that! As an aside, I've gotta say that's a great job if you can get it - reuse material you wrote at your day job, and get paid a second time to publish it in a book. Awesome!
Unfortunately, for such a detail-oriented guy in a detail-oriented field like software testing, there are a lot of mistakes in Whittaker's text. The editor, assuming they actually paid one, did a distractingly poor job, at least on the Kindle version of the book. And the sections written by Whittaker's non-writer coworkers read just like emails - typos, grammar errors, inconsistencies, and all (the guy who uses backslashes when he means forward slashes is adorable when you consider he's paid by Microsoft). The writing feels very authentic for a blog, but not up to professional-grade standards for a book.
Inside this tiny book is a focused 60-page monograph struggling to meet an editor who can dig it out and reveal its genius to the world. There's some good stuff in here, but you'll have to work for it.
EDIT: Apparently I put this review on the paperback version of the book. I actually read the Kindle version of the book. I assume the text is the same, and since I didn't comment on the binding or page material, this review should be just as relevant.
1 of 1 people found the following review helpful.
Stick to the subject
By M. Collins
This book spent so much time on subjects other than exploratory testing. The future of software testing? That's the subject for a different book. Some of the "user stories" were very poorly written. I noted a handful of typos (a QA book really shouldn't have any). I like the metaphors presented, but the takeaways could have been just as affectively written in 40 pages. It was a chore to get through this book. I'd recommend skipping it and instead searching for the touring metaphor and examples.
0 of 0 people found the following review helpful.
This is for QA entry level
By MM- NYC
This is well written, a little boring and repetitive, but overall good stuff.
I would not suggest this book to anyone who has more than 10 years on the QA field.
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker PDF
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker EPub
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker Doc
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker iBooks
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker rtf
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker Mobipocket
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, by James A. Whittaker Kindle
No comments:
Post a Comment