Książka Exploratory Software Testing James Whittaker

Exploratory Software Testing

Język: Angielski
Oprawa: Miękka
Dostępność: Dostępna u dostawcy
Wysyłamy za 5-8 dni
158.03
How to Find and Fix the Killer Software Bugs that Evade Conventional Testing In Exploratory Software...

Informacje o książce

Język
Angielski
Oprawa
Książka - Miękka
Data wydania
2009
strony
256
EAN
9780321636416
ISBN
0321636414
Enbook ID
04054742
Waga
428
Wymiary
180 x 231 x 15

Pełny opis

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?

Możesz być zainteresowany

145.66
176.92

AI ASSISTED TESTING

WINTERINGHAM MARK
239.14
251.51

A Little Life

Hanya Yanagihara
39.04

Windows Internals, Part 2

Mark E. Russinovich
239.14
99.90

Penetration Testing

Georgia Weidman
155.50
207.88
71.85

Caesar

Adrian Goldsworthy
74.48

Haikyu!!, Vol. 43

Haruichi Furudate
40.11
61.82

Given, Vol. 5

Natsuki Kizu
44.49
73.12

Klienci, którzy kupili tę książkę, kupili również

Explore It!

Elisabeth Hendrickson
108.27

Agile Testing

Lisa Crispin
199.90
188.99

Clean Code

Robert C. Martin
209.05

Full Stack Testing

Gayathri Mohan
203.79

More Agile Testing

Janet Gregory
176.04

Texture Over Taste

Joshua Weissman plton
76.14
200.87

Buddha in Testing

PRADEEP SOUNDARARAJA
79.74

Atomic Kotlin

Svetlana Isakova
225.02