Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design (Paperback)

James A. Whittaker

  • 出版商: Addison Wesley
  • 出版日期: 2009-09-04
  • 售價: $1,650
  • 貴賓價: 9.5$1,568
  • 語言: 英文
  • 頁數: 256
  • 裝訂: Paperback
  • ISBN: 0321636414
  • ISBN-13: 9780321636416
  • 相關分類: 軟體測試
  • 立即出貨 (庫存=1)



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?






- 為什麼有些錯誤對自動化測試來說是看不見的,我該如何發現它們?
- 有哪些技術可以幫助我持續發現和消除「阻礙進度」的錯誤?
- 如何使手動測試更有效,並減少無聊和不愉快的感覺?
- 每個項目的最有效的高層測試策略是什麼?
- 當無法測試所有輸入時,應該測試哪些輸入?
- 哪些測試案例可以提供最佳的功能覆蓋率?
- 如何通過結合探索性測試和傳統腳本或場景測試獲得更好的結果?
- 如何反映開發過程中的反饋,例如代碼更改?