Software Test Transfer Forms


Quick Summary
Screenshot 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.


This template requires a Premium Subscription
Please log in. Don't have a log-in? Sign up now. Already a Member? Log in to upgrade immediately and get the file! A Premium subscription is only $14.95/month or $149/year and gets you over 200 templates, guidelines, and checklists.
15-day free trial period for new Premium subscribers! Learn more
Log in to download this file

Username:  
Password:  

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.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. File the test records in a designated place for later reference if needed.

This template requires a Premium Subscription
Please log in. Don't have a log-in? Sign up now. Already a Member? Log in to upgrade immediately and get the file! A Premium subscription is only $14.95/month or $149/year and gets you over 200 templates, guidelines, and checklists.
15-day free trial period for new Premium subscribers! Learn more
Log in to download this file

Username:  
Password:  





Related Templates
Project Test Plan
Testing without a plan leads to chaos in the test phase. This plan outline walks you through the process from initial test planning to documentation and project implementation, with detailed annotations and suggestions for test types you may want to consider.




©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 info@projectconnections.com
Terms of Service and Privacy Policy

Get Our Newsletter
Get our latest content delivered to your inbox, every other week. New case studies, articles, templates, online courses, and more. Check out our Newsletter Archive for past issues.

Follow Us!
Linked In Facebook Twitter RSS Feeds

Got a Question?
Drop us an email or call us toll free:
888-722-5235
Learn more about ProjectConnections, our contributors, and our membership levels and product options.