0% found this document useful (0 votes)
61 views9 pages

FM Se 19 Test Procedures Template

The document provides test procedures for an unnamed project. It includes sections on introduction, reference documents, test cases, and procedures. The procedures consist of steps with expected results to validate requirements.

Uploaded by

bojam84386
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)
61 views9 pages

FM Se 19 Test Procedures Template

The document provides test procedures for an unnamed project. It includes sections on introduction, reference documents, test cases, and procedures. The procedures consist of steps with expected results to validate requirements.

Uploaded by

bojam84386
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

Test Procedures for insert project name

Test Procedures for: insert project name

Version: insert version number

Approval date: insert approval date

Form FM-SE-19 Test Procedures Template. Effective 6/14/2018 i


Test Procedures for insert project name

DOCUMENT CONTROL PANEL


File Name:
File Location:
Version Number:
Name Date

Created By:

Reviewed By:

Modified By:

Approved By:

Form FM-SE-19 Test Procedures Template. Effective 6/14/2018 ii


Table of Contents

1 Introduction...........................................................................................1
1.1 Purpose.................................................................................................1
1.2 System Overview..................................................................................1
1.2.1 Key Project Milestones........................................................1
1.3 System Release Description...............................................................1
1.4 Integrated Test Approach Description...............................................1
1.5 System Network Configuration...........................................................1
2 Reference Documents..........................................................................1
3 Integration (or Test) Case X Test Procedures....................................2
3.1 Requirements Testing..........................................................................2
3.1.1 Test Approach......................................................................2
3.1.2 Equipment Needed...............................................................2
[Link] Special Test Support Equipment............................................2
3.2 Test Reporting Requirements.............................................................2
4 Test Procedures....................................................................................2
4.1 Integration (or Test) Case 1 Test.........................................................2
4.1.1 Integration (or Test) Subcase 1.1..........................................3
4.1.2 Integration (or Test) Subcase 1.2..........................................3
4.1.3 Integration (or Test) Subcase 1.3..........................................3
4.1.4 Integration (or Test) Subcase 1.n..........................................3
4.2 Integration (or Test) Case 2 Test.........................................................3
5 User Definitions.....................................................................................3
List of Tables
Table 1: Title................................................................................................................... 3

List of Figures
Figure 1: Title..................................................................................................................3
List of Acronyms and Abbreviations

IC.............................................................................................................................Integration Case
TC.......................................................................................................................................Test Case
Test Procedures for insert project name

1 Introduction
Introduce the reader to the subject of the document and include a brief project description.
Provide a high-level system architecture diagram and describe the major parts of it. This can be
copied from the test plan.

1.1 Purpose
Describe the purpose of the document, how it will be used, and the testing objective(s). This can
be copied from the test plan.

1.2 System Overview


Provide a description of the system and a complete high-level system block diagram. This can be
copied from the test plan.

1.2.1 Key Project Milestones


List the key project milestones and a brief description of each if needed for clarity.

1.3 System Release Description


Describe the parts of the system that are assembled for this particular series of tests. A system
block diagram should be provided and it should relate to the system block diagram shown in the
text plan.

1.4 Integrated Test Approach Description


Describe the overall integrated test approach. This should be a summary based on the test plan
description.

1.5 System Network Configuration


Describe the system network configuration needed for this series of tests.

2 Reference Documents
List all reference material that is used in the integration and testing plan. Do not list any
documents not specifically referenced in the body of the document. The references are typically
listed as a two-column table without showing the borders. The first column includes the
document title and publishing date, while the second column includes the name and contact
information for the publisher of the document. This section always starts with the caveat:

The following documents, of the exact issue shown, form a part of this
document to the extent specified herein. In the event of a conflict between the

Form FM-SE-19 Test Procedures Template. Effective 6/14/2018 1


documents referenced herein and the contents of this document, this document
shall be considered the superseding requirement.

Include references to project-specific Florida Department of Transportation standards and


procedures used in the development of the requirements.

3 Integration (or Test) Case X Test Procedures


Describe the test set up required for this series of tests. A diagram of the test set up is
recommended that lists specifically what cables connect to what connectors, and what additional
equipment is needed to support the testing.

3.1 Requirements Testing

3.1.1 Test Approach


Briefly describe the overall test approach, including the required set up and what the test process
will be.

3.1.2 Equipment Needed


List the equipment needed for the test. This is just a list, not a detailed explanation of the pieces.
If some equipment or services are required external to the project, describe who will provide
them and how they will be injected into the testing.

[Link] Special Test Support Equipment


Describe any simulator or test data files that will be needed to conduct the testing.

3.2 Test Reporting Requirements


Briefly describe the requirements for reporting test results and what process will be followed to
dispose of any test anomalies (e.g., partial or complete failure to meet a requirement).

4 Test Procedures
This section lists the step-by-step procedures to be followed for each test. In this template, the
procedures are listed for the actual test, meaning that the first procedure will be IC 1.1 or TC 1.1.

4.1 Integration (or Test) Case 1 Test


An integration case (IC) can be all in one if it is testing one functional set of requirements, or it
may consist of multiple subcase tests that support the overall functional test. Keep the test
procedures to a manageable size where there are a maximum of 25 to 30 steps. State the test
objective for each test procedure and identify the requirements being tested.
4.1.1 Integration (or Test) Subcase 1.1

Step Procedure Expected Result Pass/Fail

Describe the step Describe the This is left blank until the test is run and then it is
1
to be taken. expected result. filled in by the test engineer.
Identify the requirements that are satisfied when
Describe the step Describe the
2 the expected result verifies that one or more of the
to be taken. expected result.
requirements have been met.
N Keep describing the steps in the procedure until the test is complete.

4.1.2 Integration (or Test) Subcase 1.2

4.1.3 Integration (or Test) Subcase 1.3

4.1.4 Integration (or Test) Subcase 1.n

4.2 Integration (or Test) Case 2 Test


Continue listing until all procedures have been included.

Table 1: Title

Figure 1: Title

5 User Definitions
DOCUMENT REVISION HISTORY
Version Approved Created/
Description of Change(s)
Number Date Modified By

You might also like