ProjectConnections Print View
888-722-5235
7am-5pm Pacific
Monday - Friday
We'd love to talk to you.
Learn more about ProjectConnections and who writes our content.
Site Help
| Content Levels | |
 | Register for free access to papers, case studies, and almost 50 templates. |
 | Subscribe for complete access: $14.95 monthly or $149/year |
| Risk-free 15-day trial!
Compare levels View sample templates Corporate subscriptions | |
Software Test Transfer Forms
Quick Summary
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
- a record of what is being transferred,
- instructions for what should be tested,
- and ultimately a record of what was tested and the results.
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.
- When the Development group has one or more new software builds ready to go to official test, fill out the Software Transfer to Test form. Indicate what modules or sub-systems are being transferred, including their part number and revision number.
- Fill out the Attachment: Re-test Instructions and Log for Issue Number _____________ for each issue the Development group is ready to have a Tester verify. Include any special instructions for how the issue should be thoroughly verified, and specify what regression tests on other functionality should be done to ensure the fix didn't break something else.
- The tester(s) receive the forms and run the tests, checking off tests, recording test steps and results as they go, and signing and dating each Re-test sheet as they finish testing that issue.
- The testers then complete the System Regression Testing specified on the Software Transfer to Test form, make a recommendation at the bottom of the form as to whether these software builds are ready for a real release (have all the problems been corrected, and nothing broken?), and return the test results to Development.
- File the test records in a designated place for later reference if needed.
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy