The issues are simple and so are the questions
underlying them. The answers to those questions must be equally simple to be useful. Getting the
answers
isn??™t
simple and that??™s why a lot of this book is devoted to how the test manager gets
answers and interprets them.
??? Chapter 3 begins the discussion of
risk
, which carries on throughout the book.
??? Chapter 4 tells you how to
plan and manage tests
, and discusses possible starting points.
??? Chapter 5 looks at
web
testing.
??? Chapter 6 puts testing into the context of several
life-cycle models
.
??? Chapter 7 and Chapter 8 look at the things you must do and have ready for use, your
tools,
processes, and support systems
, your eyes and ears, the kinds of testing you may need to do, and
the documents you need to work with.
??? Chapter 9 examines the
test team
in its context, who they interact with, how, and why.
??? Chapter 10 looks at the problems of
outsourcing
, third-party service provisions, and how to
accept a release.
??? Chapter 11 through Chapter 13 look at
test techniques
in as much detail as you will need to
know, and show how they get you the answers you need.
xx
Manage Software Testing
??? Chapter 14 covers
unit testing
and why it will save you time and money by reducing risk during
system testing.
??? Chapter 15 through Chapter 17 go into
system, performance, and usability
testing.
??? Chapter 18 deals with the issues needing to be backed by
metrics
.
Pages:
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76