Practical forms to accompany a software build when Development sends it Testing, to serve as a record of what is being transferred, testing instructions, and ultimately a record of what was tested and the results.
What this is
Forms to accompany a software build when it is handed over from Development to a Test group for verification that issues recorded in previous testing have been resolved. This file includes a template for the form that communicates what software is being sent to test, as well as a template for "issues testing", to indicate what tests should be run to verify correction of each issue.
This particular version is geared to an environment where multiple software subsystems are part of a hardware-software system or product. It therefore includes fields for indicating what software sub-systems are being transferred to Test at this time.
The Software Transfer to Test form includes space to list what issues have supposedly been resolved, and instructions for what system regression tests should be done as well.
The second form is meant to be used as an attachment, with one sheet filled out per issue that has been corrected.
Both forms serve as
Why it's useful
Even in the smallest development environments, it's important to have an orderly process for correcting software issues (defects or "bugs" or problems discovered during testing) and feeding the updated software back for re-test. This retest should ensure that the bugs the developers think they have corrected really are fixed, AND that nothing else has been broken by the fix!
These forms were created by a company developing a relatively complex electro-mechanical, software-controlled system. The company did not yet have a well-established, formal test group or test processes. As they approached the release of the new system, they had to turn around software fixes quickly, and found that it was easy to lose track of what had been tested, which version certain bugs had been corrected in, and whether they had regression tested consistently. They needed a simple approach for ensuring orderly testing and good test records, while not slowing down the team's rapid iterations.
How to use it
Modify the fields on the forms as needed to match your particular environment, then use them in the following manner.
©Copyright 2000-2017 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail firstname.lastname@example.org