Wait until the end of the test and then gently ask the project manager
if he could have found a quarter of what the test team found. In front of the test team.
60 Manage Software Testing
??“ That testers will review the baseline for the tests and be able to have it changed
??“ On the risk and responsibility for premature releasing
4.6.2 Test Inputs
You must have access to the following:
??? A baseline against which to test. (Needn??™t be a specification. Could be just an earlier version of
the system. Must be unambiguous.) If you don??™t have this (because the developers are just throwing
the software over the wall), then you must be free to create one as you go. Start with the user
manual. If you can??™t get a baseline then it will be impossible for you to determine if:
??“ The developers have included that feature in the release
??“ You??™ve found a bug or a feature
??“ The bug??™s been fixed
??“ You??™ve tested that feature already
??“ Whether a bug is serious or trivial7
??? A way of managing that baseline. The baseline will change. If that change is unclear or if you??™re
not aware of the change, you may not know until enraged customers call.
??? A basis for determining the severity of a bug. Sounds obvious but it isn??™t. The seriousness of a
bug can be measured in terms of what it will cost you (the test manager), the test team, the
developers, the company, and of course the customer, and the customer??™s customers.
Pages:
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191