Mensys Online Shop
| Categorie: | Algemeen - Boeken | Van: | Addison Wesley US |
| Meer informatie: | www.awprofessional.c... | Auteur(s): | James A. Whittaker |
| Bladzijden: | 224 | Publicatie-jaar: | 2010 |
Whittaker defines both in-the-small techniques for individual testers & 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 » Lees meer... |  |
Alle prijzen zijn in Euro excl. BTW (19%, voor boeken 6%) en excl. verzendkosten.
E-mail of bel 023 548 20 20 voor licenties, upgrades en andere vragen.
Whittaker defines both in-the-small techniques for individual testers & 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 & eliminate 'show stopper' bugs?;- How do I make manual testing more effective - and less boring & 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?