Scribd
Upload
605 views5 pages

Software Test Report Template

This software test report summarizes testing of a project/product and its versions. It provides details on test dates and resources used, what was tested and what issues were discovered. Testing identified some requirements that could not be fulfilled and major bugs. Some issues will be deferred to future releases, while others have workarounds documented. The report recommends the software for a beta release provided outstanding issues are approved.

Uploaded by

srinik123
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
605 views5 pages

Software Test Report Template

This software test report summarizes testing of a project/product and its versions. It provides details on test dates and resources used, what was tested and what issues were discovered. Testing identified some requirements that could not be fulfilled and major bugs. Some issues will be deferred to future releases, while others have workarounds documented. The report recommends the software for a beta release provided outstanding issues are approved.

Uploaded by

srinik123
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 5

SOFTWARE TEST REPORT:

Project/Product Name and Version(s)

Approvals
Approved By: Signature Date
Approver Name Signature Date

Software Test Report 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
Name Full name of the product(s) being release
Version Version number (plus internal version number)

3. DATES
Test Start Date Formal test start date (how did this compare
against plan?)
Test Complete Date Formal test end date (how did this compare
against plan?)
Test Days – Duration Duration is the number of calendar days that the
test phase spanned
Test Days – Effort The test effort is the sum of all the work days of
all the test team over the test duration

4. RESOURCES

4.1. People
Test Lead Name
Test Analyst Name
Development Lead Name
Developer Name
Business Analyst Name
Etc. Etc.

4.2. Environment
Test Rigs Give spec of hardware
Test PCs Give spec of hardware
Test Server Give spec of hardware
Production Server Details of server names/addresses, etc.
Etc. Etc.

Software Test Report 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 1 Tool name (and version)
Tool 2 Tool name (and version)
Tool 3 Tool name (and version)
Tool 4 Tool name (and version)

5.3. What Was Tested


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

5.4. What Was Not Tested


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

6. ISSUES RAISED
Issues Raised Number of bugs and change requests raised.
Software Test Report Page 3
You may wish to give separate totals for bugs
and change requests.
Issues Closed Number of bugs and change requests closed
Issues Deferred to Number of bugs and change requests deferred
Future Releases
Issues Outstanding 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.

6.1. Issues Outstanding


State the total number of issues outstanding here.

ID The unique ID number of the issue


Severity e.g. Medium
Type Bug or change request
Summary One line summary of the issue
Workaround 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.
Plan State what the plan is to finally resolve this issue for
the live production environment. This sets the user
expectation.

ID
Severity
Type
Summary
Workaround
Plan

ID
Severity
Type
Summary
Workaround
Plan

ID
Severity
Type
Summary
Workaround
Plan

ID
Software Test Report Page 4
Severity
Type
Summary
Workaround
Plan

ID
Severity
Type
Summary
Workaround
Plan

7. RECOMMENDATIONS
Recommendation 1 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.”
Recommendation 2 etc.

Software Test Report Page 5

You might also like