5.2 Starting Up a New Test Function
You are faced with absolutely nothing. No lead testers, no testers, no tools. You have to recruit everyone.
There may be a very good reason why they are only now starting a test function, which, if you are wise,
you will discover. (When is the release date? How long?) The best possible reasons are (in descending
order of attractiveness):
??? That everything is new, and a far-sighted project director wants to have a Testing function as fast
as possible, even before requirements are written.
??? That testing was hitherto informal but it happened, and now it??™s getting too big and needs to be
managed.
??? That testing was done by some other group which is now to be (or has just been) sacked.
Write a report on the status of the project. Look particularly at any results obtained so far. See section
A.10 in Appendix A. Then write your test strategy document. You are probably very lucky in that you
have a green-field to work on.
4.5.3 Taking Over an Old Test Function
Your predecessor left for some very good reasons. Make sure they were only salary- or competencerelated.
Spend some time assessing where you are now with the aid of the checklists in Appendix B.
Remember:
??? There is no advantage in change for change??™s sake.
??? To ask testers, developers, and management how much value the test team has added so far.
??? To listen for the sound of people being tactful. An old test function might also be a failing test
function (see below).
Pages:
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185