246
Manage Software Testing
iii. (Ongoing) Review the tests and the process of building them.
iv. (Ongoing) Identify the smoke and confidence tests, and automate them.
5. Hold a test readiness review. See section 6.6. This may reveal that you are not ready to run the
tests because:
a. They??™re not all written because your planning was amiss: admit failure to your manager, work
out what can be run, and put in place a plan to write the rest. Maybe the features wouldn??™t
have been ready in time anyway.
b. They can??™t be run on the environment as it is: identify what needs to be changed, and issue a
memo to identify what needs changing or adding, and the control you need over the environment.
c. The requirements have changed or continue to change. As a. above.
d. (Some) Tests cannot be run because the code isn??™t ready: identify which and issue a memorandum
to the parties concerned.
6. (Per build) Test a build. Report the bugs found.
a. Accept a release. Run the smoke and confidence tests.
b. (Ongoing) Write the bug reports.
7. (Ongoing) Report:
a. To the project manager and other stakeholders.
b. Write the post-release report.
c. Run the smoke and confidence tests on each build.
d. Run the tests on each build.
e. Write the weekly reports.
8. (Ongoing) Monitor the test process.
a. Identify your priority actions and the dates by which they must be achieved; this is where the
test strategy document discussed
in section 8.
Pages:
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473