They are a mine of knowledge about the history of the product,
the horrors of the last release, and configuration testing.
22. Test manager is in charge of writing the test strategy, and test plan, or the test parts of the quality
plan. He may report to the project manager or to the line manager. As such he may come under
pressure to cut corners. This would be very serious if no quality assurance manager or quality
assurance representative exists to whom he could turn to limit that pressure. He must run the
testing group and be the principal conduit through which test result are made known to the
project. He reviews tests. He must have a separate exception reporting line to someone with a
major and financial stake in the success of the project, such as the managing director, the project
director, or the line manager.6 He may be in a position to refuse to make a release. He must always
be able to refuse to sign-off a release.
23. Testers are responsible for controlling the quality of deliverables by specifying, writing, executing,
and analyzing tests; may also be programmers though they will not be the same staff responsible
for writing the system/components to be tested. They need testable specifications, releases, and
your support. They should also be reviewing the specifications. They report to the test manager
but may indirectly report to the project manager should they be split among feature teams.
There is inevitably an adversarial relationship between testers and developers.
Pages:
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110