??? Evaluate the results.
??? Write the bug reports.
??? Correct any bugs discovered.
??? Write the system test summary report.
??? Update the system test specifications, procedures, and software.
??? Modify the tests.
90
Manage Software Testing
??? Review the number of bugs expected to be found.
??? Get the system to a sufficiently stable state to allow customer representatives to attend the acceptance
test.
See Chapter 15 for more on this.
6.8 Beta Testing
Beta testing is the moment your wonderfully-crafted product finally arrives before ???real??? users. You need
to balance the amount of effort you need to do it, with the minimal response they mostly give you.
Beta testers:
??? Are the nearest you will get to real-world users.
??? Are sometimes from companies whose senior staff are old friends of the marketing people. The
other staff will know this and may resent it since they never get taken out to lunch.
??? Have many other things to do besides play with your software. So you need to look at why they
would do it anyway:
??“ Because they already use the software and they want to know:
??? If it??™s worth continuing with it,
??? If the features they??™ve been screaming at you for the last 18 months are finally there.
??“ Because they might, just possibly, recommend it for purchase, and taking part in the beta test
process is the cheapest way of accessing a copy.
??? Aren??™t testers. They??™ve (mostly) no idea of how to report a bug, and will happily tell you everything
is wonderful, even when they??™ve given up on the software upon seeing how big the manual is.
Pages:
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244