Manage Software Testing
Features
Summary
Whether you are inheriting a test team or starting one up, Manage Software Testing is a must-have resource that covers all aspects of test management. It guides you through the business and organizational issues that you are confronted with on a daily basis, explaining what you need to focus on strategically, tactically, and operationally.
Using a risk-based approach, the author addresses a range of questions about software product development. The book covers unit, system, and non-functional tests and includes examples on how to estimate the number of bugs expected to be found, the time required for testing, and the date when a release is ready. It weighs the cost of finding bugs against the risks of missing release dates or letting bugs appear in the final released product.
It is imperative to determine if bugs do exist and then be able to metric how quickly they can be identified, the cost they incur, and how many remain in the product when it is released. With this book, test managers can effectively and accurately establish these parameters.
Table of Contents
Preface
Introduction
The Big Questions You Need Answers To
Risk Management
Test Planning and Management
Testing and the Web
The Overall Test Life-Cycle
Testing Processes and Infrastructure
Test Documents
The Test Team and Its Context
Outsourcing
Test Techniques–Functional (Black-Box)
Test Techniques–Structural (White-Box)
Test Techniques–Static Analysis
Unit Test Process
System and Acceptance Testing
Performance and Stress Testing
Usability Test Process
Metrics
Appendix–Examples
Appendix–Checklists
Appendix–Category and Priority Classifications for Bug
Reporting
Appendix–Tools
Appendix–References
Glossary
Index
Illustrations
Tables
Editorial Reviews
"…a comprehensive, practical cookbook of software testing with a slight mix of quality spices. …the book is a step-by-step guide of how to perform testing. It is practically focused and, in many of the chapters, the reader can follow the tasks (as if they were recipes) when performing testing activities."
-Software Testing, Verification & Reliability, Vol. 15, No. 3, Sept. 2005
