Scribd
Upload
217 views

Software Test Procedure Specification Template

This document provides a template for test procedure specifications according to the IEEE 829-1998 standard. The template includes sections for test procedure identifier, purpose, special requirements, and steps. The identifier section specifies unique identification information. The purpose section lists test cases covered and describes the procedure. The special requirements section specifies if the procedure is manual or automated, required test stages, environment, and skills. The steps section outlines the activities to execute the procedure such as set-up, start, measure, and shutdown.

Uploaded by

Amadeo Garcia
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
217 views

Software Test Procedure Specification Template

This document provides a template for test procedure specifications according to the IEEE 829-1998 standard. The template includes sections for test procedure identifier, purpose, special requirements, and steps. The identifier section specifies unique identification information. The purpose section lists test cases covered and describes the procedure. The special requirements section specifies if the procedure is manual or automated, required test stages, environment, and skills. The steps section outlines the activities to execute the procedure such as set-up, start, measure, and shutdown.

Uploaded by

Amadeo Garcia
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Test Procedure Specification Template

(IEEE 829-1998)
Test Procedure Specification Identifier

Some type of unique company generated number to identify this test procedure specification,
its level and the level of software that it is related to. Preferably the procedure specification level
will be the same as the related software level. Ideally the procedure naming convention should
follow the same general rules as the software it is related to. This is to assist in coordinating
software and testware versions within configuration management.

• Unique "short" name for the procedure


• Version date and version number of procedure
• Version Author and contact information
• Revision history

Purpose

• List all test cases covered by the procedure


• Description of the procedure

Special Requirements

• Manual or Automated
• Stages in which test is to be used (pre-testing, repair and regression testing, future
compliance testing, end-to-end testing, re-testing after certification, etc.)
• Test environment
• Special skills or training required (especially if automated)
• Any prerequisite procedures

Steps

What are the activities associated with the procedure. Include any of the following activities that
may be required to execute the procedure.

• Log
• Set-up
• Start
• Proceed
• Measure
• Shutdown
• Restart
• Stop
• Wrap-up

2001 - Software Quality Engineering - Version 7.0


A - 21
• Contingencies

2001 - Software Quality Engineering - Version 7.0


A - 22

You might also like