[go: up one dir, main page]

0% found this document useful (0 votes)
108 views11 pages

TSR-IEEE Template

This document provides a test summary for a project. It describes the test strategy, which includes unit, component, and system testing conducted between specified dates. It defines test result classifications as OK, NOK, POK, NRUN, and NCOM. The test preparation section outlines the necessary hardware, software, and other preparations needed before executing the tests, including any safety, security, and privacy precautions.

Uploaded by

Afrina Zainudi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
108 views11 pages

TSR-IEEE Template

This document provides a test summary for a project. It describes the test strategy, which includes unit, component, and system testing conducted between specified dates. It defines test result classifications as OK, NOK, POK, NRUN, and NCOM. The test preparation section outlines the necessary hardware, software, and other preparations needed before executing the tests, including any safety, security, and privacy precautions.

Uploaded by

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

Test Summary Document

for

[Project]

Version [1.0]
<Note: Must follow the latest number in Revision History table.>

Prepared by

[Team]
[List of Name (Student Id)]

[Date Created]
<Note: Must follow the latest date in Revision History table.>

Copyright © 2007 by Strong QA Ltd. Permission is granted to use, modify, and distribute this document.
Software Test Document for [Project] Page ii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History............................................................................................................................iii
1. Introduction..............................................................................................................................1
1.1 Purpose.........................................................................................................................................1
1.2 Definitions, Acronyms and Abbreviations...................................................................................1
1.3 Intended Audience and Reading Suggestions..............................................................................1
1.4 Product Scope...............................................................................................................................1
1.5 References....................................................................................................................................1
2. Test Overview...........................................................................................................................2
2.1 Strategy.........................................................................................................................................2
2.2 Result Classifications...................................................................................................................2
3. Test Preparation.......................................................................................................................3
3.1 Hardware......................................................................................................................................3
3.2 Software........................................................................................................................................3
3.3 Other.............................................................................................................................................3
3.4 Safety, Security And Privacy Precautions....................................................................................3
4. Test Summary..........................................................................................................................4
4.1 Unit Testing..................................................................................................................................4
4.2 Component Testing.......................................................................................................................4
4.3 System Testing.............................................................................................................................4
5. Test Results...............................................................................................................................5
5.1 Test Instances...............................................................................................................................5
5.2 Recommendations........................................................................................................................5
Appendix A: Approval..................................................................................................................6
Appendix B: Glossary....................................................................................................................7
Appendix C: To Be Determined List............................................................................................8
Software Test Document for [Project] Page iii

Revision History
Name Date Reason For Changes Version
Software Test Document for [Project] Page 1

1. Introduction

1.1 Purpose
<Note: Identify the product whose software testing are specified in this document, including the
revision or release number. Describe the scope of the product that is covered by this TSD,
particularly if this TSD describes only part of the system or a single subsystem.>

1.2 Definitions, Acronyms and Abbreviations


<Note: Describe any standards or typographical conventions that were followed when writing this
TSD, such as fonts or highlighting that have special significance. For example, state whether
priorities for higher-level requirements are assumed to be inherited by detailed requirements, or
whether every requirement statement is to have its priority.>

1.3 Intended Audience and Reading Suggestions


<Note: Describe the different types of readers that the document is intended for, such as
developers, project managers, marketing staff, users, testers, and documentation writers. Describe
what the rest of this TSD contains and how it is organized. Suggest a sequence for reading the
document, beginning with the overview sections and proceeding through the sections that are most
pertinent to each reader type.>

1.4 Product Scope


<Note: Describe the boundaries of the design here. State what functionality is included and what is
excluded. This statement is given in terms of business functions.>

1.5 References
<Note: The following references are cited in this document:

 [SRS] Please refer to the latest approved version of the document <Put SRS title here>.
<Please provide the hyperlink to the library containing this SRS for the SRS title>
 [SDD] Please refer to the latest approved version of the document <Put SDD title here>.
<Please provide the hyperlink to the library containing this SRS for the SDD title>
 [Traceability Matrix TM)] Please refer to the latest approved version of the document. TM
can be use to trace all requirements related to the component.<Put TM title here>. <Please
provide the hyperlink to the library containing this RTM for the TM title>

(Optional) – Note any references or related materials here. (Some other technical documents like:
IETF, RFC… that you mentioned above.)>
Software Test Document for [Project] Page 2

2. Test Overview

2.1 Strategy
<Note: Give a few information about how the project being tested.

The XXX software (version x.y.z) was tested on the xxx test platform located in xxx, from the
[starting sate] to the [ending date]. There are three type of testing being conducted. These testings
are;
1. Unit testing ([starting date] to [ending date])
2. Component testing ([starting date] to [ending date])
3. System testing (([starting date] to [ending date]).>

2.2 Result Classifications


The software testing results are defined according to the following rules:

1. 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.
2. NOK: The test sheet is set to "NOK" state when all steps of the test are set to "NOK" state or
when all of the result of a step differs from the expected result.
3. POK: The test sheet is set to "POK" state when at least one of the test is set to "NOK" state or
when the result of a step is partially compliant to the expected result.  Keep it or remove.
Source of inconsistencies: criteria to set if result is Partial OK may be qualitative
4. NRUN: Default state of a test sheet not yet executed.
5. NCOM: The test sheet is set to "Not Completed" state when at least one step of the test is set
"Not Run" state.
Software Test Document for [Project] Page 3

3. Test Preparation
<Note: This section contains tasks and recommendations before executing tests.

Describe the tests preparation tasks, for a phase, a category of tests, or even a single test (in this
case, use the test identifier).

Give a name to sub-sections, which matches the scope of described tasks..>

3.1 Hardware
<Note: Describe platform configuration operations, like specific hardware to be used, physical
network configuration.

You may add a diagram and steps to set up hardware for use.>

3.2 Software
<Note: Describe software set-up and configuration operations, like simulators or software test tool
to be used, logical network configuration.

You may add a diagram and steps to set up software for use.>

3.3 Other
<Note: Describe here any other specific task to do before tests.>

3.4 Safety, Security And Privacy Precautions


<Note: Add here warnings or precautions about safety, security and privacy.
Think twice about it if tests are, for example, realized in a health care center.>
Software Test Document for [Project] Page 4

4. Test Summary
<Note: Include basic information about what was tested and what happened.>

4.1 Unit Testing


<Note: Include basic information about what was tested and what happened.>

4.1.1 Class 1: [Class’s Name]

<Note: You may attach all related Software Testing Sheet with thw class. Please repeat for every
classes>

4.2 Component Testing


<Note: Include basic information about what was tested and what happened.>

4.2.1 Interface 1: [Class 1’s Name and Class 2’s name]

<Note: You may attach all related Software Testing Sheet with thw class. Please repeat for every
component tests>

4.3 System Testing


<Note: Include basic information about what was tested and what happened.>

4.3.1 [System Test Name – Integration, Regression, System etc.]

<Note: You may attach all related Software Testing Sheet with thw class. Please repeat for every
system tests>
Software Test Document for [Project] Page 5

5. Test Results
<Note: Summarize the test results. Include a detailed description of any deviations from the
original test plan, design, test case, or expected results. Include any issues or bugs discovered
during the test.>

5.1 Test Instances


<Note: Provide a brief description of the unexpected results, problems, or defects that occurred
during the testing.>

5.1.1 Resolved Test Incidents

<Note: Identify all resolved test incidents and summarize their resolutions. Reference may be
made to Test Incident Reports that describe in detail the unexpected results, problems, or defects
reported during testing, along with their documented resolutions, which may be included as an
appendix to this document.>

5.1.2 Unresolved Test Incidents

<Note: Identify all unresolved test incidents and provide a plan of action for their resolution.
Reference may be made to Test Incident Reports that describe in detail the unexpected results,
problems, or defects reported during testing, which may be included as an appendix to this
document.>

5.2 Recommendations
<Note: Describe what actions are suggested upon completion of this test. Provide any
recommended improvements in the design, operation, or future testing of the business product that
resulted from the testing being reported. A discussion of each recommendation and its impact on
the business product may be provided. If there are no recommendations to report, then simply
state as such.>
Software Test Document for [Project] Page 6

Appendix A: Approval
The undersigned acknowledge they have reviewed the [Project Name] Test Summary Report and agree with
the approach it presents. Changes to this Test Summary Report will be coordinated with and approved by the
undersigned or their designated representatives.

<Note: List the individuals whose signatures are desired. Examples of such individuals are Quality
Manager or Tester. Add additional lines for signature as necessary. Although signatures are
desired, they are not always required to move forward with the practices outlined within this
documentation.>

1. Signature: _______________________________________ Date: _____________


Name: _______________________________________
Student Id: _______________________________________
Role: _______________________________________

2. Signature: _______________________________________ Date: _____________


Name: _______________________________________
Student Id: _______________________________________
Role: _______________________________________

3. Signature: _______________________________________ Date: _____________


Name: _______________________________________
Student Id: _______________________________________
Role: _______________________________________
Software Test Document for [Project] Page 7

Appendix B: Glossary
<Note: Define all the terms necessary to properly interpret the TSR, including acronyms and
abbreviations. You may wish to build a separate glossary that spans multiple projects or the entire
organization, and just include terms specific to a single project in each TSR.>
Software Test Document for [Project] Page 8

Appendix C: To Be Determined List


<Note: Collect a numbered list of the TBD (to be determined) references that remain in the SDD so
they can be tracked to closure.>

You might also like