An easy to read book written for someone who is currently, or about to manage a testing team. The author has spent 14 years in testing and quality assurance. The book is based on the author's experiences and is realistic in its expectations of what will happen in a real-life test project.
The book includes descriptions of how to develop some essential tools and apply them to a test project. The author describes the people management techniques that can help you get the resources from your manager that you'll need in order to succeed, as well as how to deal with your peers within the organisation. The descriptions and examples given for a hardware and a software project.
Note however, that the book deals with managing the testing process. It covers what you'll need to test and at a superficial level how to go about testing, but it does not provide detailed test cases, details of how to develop them or what a specific test case should include.
Test Escapes, coverage and regression test gaps.
Describes why you need a bug tracking database and what it should contain; bug report, ranking (severity, priority & Risk Priority Numbers), bug states, ownership, history, subsystem, configuration, close date, resolution and root cause.
As an aside the chapter describes how a bug report should be written and what it should and should not include and the important difference between bug isolation and debugging.
The chapter describes how the bug data collected can be used; (Opened/closed chart, Root cause chart, Closure period chart, Subsystem chart).
The chapter concludes with a review of managing bug tracking and the politics related to bug data.
to dolist with status tracking and summary capabilities.
Deals with the realities of the test process once it is underway. The chapter starts with observations on crunch mode
and some tips on how to survive it.
The chapter introduces two tools designed to help you manage the testing processes. One is a logistics database to track the locations, configurations and test requirements for hardware, software, infrastructure and staff. The second is a simple change management database to help you respond to the changes that occur during the test project.
Discusses how office politics
affect how your role as a test manager is seen in the company and how to communicate with and get support from other managers.
How various organisational models will effect the operation of the test department is also discussed.