SOFTWARE TEST REPORT: Project/Product Name and Version(s)

Approvals
Approved By: Signature Date

Approver Name

Signature

Date

Software Test Report Created by http://www.The-Software-Tester.com

Page 1

1.

OVERVIEW

[** Note: Text listed in green is for information only and should be removed. This can be done by selecting the Normal style from the Styles and Formatting menu option. **] Summarise the test phase here, pulling out the most important outcomes of the testing, e.g. any requirements which could not be fulfilled, significant changes made to requirements, major bugs that were found, significant issue that are to be carried forward, etc.

2.

SOFTWARE IDENTIFICATION
Full name of the product(s) being release Version number (plus internal version number)

Name Version

3.

DATES
Formal test start date (how did this compare against plan?) Formal test end date (how did this compare against plan?) Duration is the number of calendar days that the test phase spanned The test effort is the sum of all the work days of all the test team over the test duration

Test Start Date Test Complete Date Test Days Duration Test Days Effort

4.
4.1.

RESOURCES
People
Name Name Name Name Name Etc.

Test Lead Test Analyst Development Lead Developer Business Analyst Etc.

4.2. Environment
Test Rigs Test PCs Test Server Production Server Etc.
Software Test Report Created by http://www.The-Software-Tester.com

Give spec of hardware Give spec of hardware Give spec of hardware Details of server names/addresses, etc. Etc.
Page 2

4.3. References
Reference ID #1 Hyperlink to references like Requirements Specification, Functional Specification, Test Specification, etc.

5.

TESTING

5.1. Methodology
This should reflect the Test Approach section in the Test Plan (or Test Specification). If it became necessary to use different techniques and methods as testing progressed then document these changes here. Otherwise try and be as brief as possible and simply refer back to the original document.

5.2. Tools
Tool Tool Tool Tool 1 2 3 4 Tool Tool Tool Tool name name name name (and (and (and (and version) version) version) version)

5.3. What Was Tested

Area or component or screen, etc., that was tested. Could also be load or performance testing, etc. One row per item. etc. etc. etc. etc. etc. etc. This should be as documented in the Test Plan or Test Specification. If different then mention those differences here.

etc. etc. etc. etc. etc. etc.

5.4. What Was Not Tested

State items or areas that were not tested. etc. etc. etc. Give the reason for not testing. etc. etc. etc.

6.

ISSUES RAISED
Number of bugs and change requests raised.
Page 3

Issues Raised
Software Test Report

Created by http://www.The-Software-Tester.com

Issues Issues Future Issues

Number of bugs and change requests outstanding Paste in a copy of the defect discovery profile/chart here if you have one. This gives a visual representation of the bugs and change requests raised and fixed throughout the test phase.

Closed Deferred to Releases Outstanding

You may wish to give separate totals for bugs and change requests. Number of bugs and change requests closed Number of bugs and change requests deferred

6.1. Issues Outstanding

State the total number of issues outstanding here. ID Severity Type Summary Workaround The unique ID number of the issue e.g. Medium Bug or change request One line summary of the issue If there is a workaround that mitigates the issue then give it here. This can be useful information that can find its way into the Release Notes or equivalent documentation. State what the plan is to finally resolve this issue for the live production environment. This sets the user expectation.

Plan

ID Severity Type Summary Workaround Plan ID Severity Type Summary Workaround Plan ID Severity Type Summary Workaround Plan ID
Software Test Report Created by http://www.The-Software-Tester.com Page 4

Severity Type Summary Workaround Plan ID Severity Type Summary Workaround Plan

7.

RECOMMENDATIONS
Summary of first recommendation (if any). For example, This software is suitable for release to the beta environment provided that the known outstanding issues and workarounds are approved by the project management team. etc.

Recommendation 1

Recommendation 2

Software Test Report Created by http://www.The-Software-Tester.com

Page 5