??? That you can be faced with a number of test leaders each of whom has their own view of what
testing is about. They may tell you something new. You may have to tell them something they
need to know. Establish yourself. Nicely. Out there are people who need you and are prepared to
like what you do. Be prepared to explain. Be prepared to insist on essentials.
??? To look at the tests and the testers. Review both, and trace some tests back to their baseline(s).
Trace some other baselines back to the tests.
??? To look at the user group message boards. Are there signs of people giving up with the company?
Write a report on the status of the function. Look particularly at the results. See section A.10 in Appendix
A. Look at:
??? Proportion of developer hours versus tester hours
??? Proportion of bugs found before release compared with those found after release
??? Number of pages of requirements/functional specifications, for each release compared to the
number of tests for the last 3 releases. How much has that proportion varied?
??? Proportion of requirements covered by tests
For indications of what is going wrong as well as the checklist in section B.7 in Appendix B.
5 ???Investment analysts only hold a stock for 6 months.??? Clarence H. Brooks, private communication.
58 Manage Software Testing
4.5.4 Reforming a Failing Test Team
How did management know the function was failing? (Table 4.1)
Test functions fail for several reasons:
??? The decision to release was taken with out reference to the test team.
Pages:
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186