This book is intended, among other things, to remind everyone that testing occurs for good reasons,
and these need to be made explicit if they are to be understood. The place for this is not the test plan
but the test strategy document. See
section 8.3
.
See also [Minto] for good ways of thinking and writing
strategically.
The test strategy document is a way of exposing your thoughts on what you are testing and why. It
provides the rationale for the test plan and the overall approach to testing, and thus helps you to keep such
thoughts in a place where they are more likely to be read. To some extent it subsumes some of the contents
of the quality plan (see
section 8.21), while leaving (say) the activities and the schedule to change as progress
dictates. As a manager you must be able to work part of your time at a strategic level so that you can align
your work with the company??™s needs. You will be expected to share your strategic thoughts with other
managers and of course the board. Use the test strategy document for this.
1.8.3 Planning and Specifying
Testing takes time. So you need a test plan to manage that time. Tests get planned in test plans. These
may be self standing or part of quality plans (see
section 8.21 in Chapter 8). Generally speaking, quality
plans define a project??™s overall approach to quality, and thus shouldn??™t change throughout the project??™s
life unless something most important happens.
Pages:
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99