Page 1 / 6

Software Test Report

for
<Project name>
Version <X.X>

<Doc. No. : xxxx-xxx-xx>

 Page 2 / 6

Revision History
Date Rev. Description Prepared by Approved by
 Page 3 / 6

TABLE OF CONTENTS
1 Introduction 4
1.1 Document overview 4
1.2 Abbreviations and Glossary 4
1.2.1 Abbreviations 4
1.2.2 Glossary 4
1.3 References 4
1.3.1 Project References 4
1.3.2 Standard and regulatory References 4
2 Overview of Tests Results 5
2.1 Tests log 5
2.2 Rationale for decision 5
2.3 Overall assessment of tests 5
3 Detailed Tests Results 6
3.1 Sub section name 6
 Page 4 / 6

1 Introduction

1.1 Document overview

This document is the software test report of the xxx testing phase of the XXX software
development project. It contains the results of tests, which were executed during the testing
phase xxx.

1.2 Abbreviations and Glossary

1.2.1 Abbreviations
Add here abbreviations

1.2.2 Glossary
Add here words definitions

1.3 References

1.3.1 Project References

# Document Identifier Document Title

[R1] ID Add your documents references.
One line per document

1.3.2 Standard and regulatory References

# Document Identifier Document Title

[STD1] Add your documents references.
One line per document
 Page 5 / 6

2 Overview of Tests Results

2.1 Tests log

Give a few information about tests.
The XXX software (version x.y.z) was tested on the xxx test platform located in xxx, from the
yyyy/mm/dd to the yyyy/mm/dd. The tests of the test phase (ref. software test plan) where
executed.
Testers where:
• John Doe,
• Marc Smith

2.2 Rationale for decision

After executing a test, the decision is defined according to the following rules:
• OK: The test sheet is set to "OK" state when all steps are in "OK" state. The real result is
compliant to the expected result.
• NG: The test sheet is set to "NG" state when all steps of the test are set to "NG" state or
when the result of a step differs from the expected result.

2.3 Overall assessment of tests

Give a qualitative overall assessment of tests.
Example:
• All tests with interfaces passed, graphical user interface is not optimized for screens of
the test platform
• All tests passed but software is too slow for acceptable use
• …

Give quantitative results.

Statistics about tests:
• % of tests OK,
• % of tests NG
 Page 6 / 6

3 Detailed Tests Results

3.1 Sub section name

Test ID T-SRS-REQ-001-XX Description

Test description Verify that the xxx software
receives data from yyy
Verified SRS-REQ-001
Requirement
Initial conditions The state of software before You may reference a procedure or it may
test be the result of previous test
Ex : XXX Software is started
YYY simulator is started
Tests inputs Input data from any test You may reference a procedure to use
tool, input files name and the test tool
location
Data collection Recording and post You may reference a procedure to record
actions processing of output data data with a test tool
Tests outputs Output data files names and Give unique name out output data files.
location, logs …
Assumptions and If any, may be limited access
constraints to a tool, license …
Ex : YYY simulator work
only in the range of zzz
Expected results List here the results of test
and criteria
Test procedure
Expected result and
Step number Operator actions Result Tester
evaluation criteria
1 Send data with YYY Simulator displays msg
simulator “data sent”
2 Open xxx window of Sent data are displayed,
xxx software with date-time of
reception
3 Press run button Sent data are processed,
result is displayed.
Value of result is …