Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design
-
- Taschenbuch ausgewählt
- eBook
-
Sprache:Englisch
37,99 €
UVP
42,99 €
inkl. gesetzl. MwSt.,
Beschreibung
Produktdetails
Einband
Taschenbuch
Erscheinungsdatum
25.08.2009
Verlag
Pearson Education LimitedSeitenzahl
256
Maße (L/B/H)
23,2/17,8/1,5 cm
Gewicht
408 g
Auflage
1
Sprache
Englisch
ISBN
978-0-321-63641-6
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?
Noch keine Bewertungen vorhanden
Verfassen Sie die erste Bewertung zu diesem Artikel
Helfen Sie anderen Kundinnen und Kunden durch Ihre Meinung.
Kurze Frage zu unserer Seite
Vielen Dank für dein Feedback
Wir nutzen dein Feedback, um unsere Produktseiten zu verbessern. Bitte habe Verständnis, dass wir dir keine Rückmeldung geben können. Falls du Kontakt mit uns aufnehmen möchtest, kannst du dich aber gerne an unseren Kund*innenservice wenden.
zum Kundenservice