Test Procedure

Go up to Terms and Definitions

A Test Procedure specifies the ordered activities that implement part or all of a Test Definition during a Test Execution.

The Test Procedure translates the intent and conditions of the Test Definition into executable activities. These activities include preparing the Test Environment, establishing preconditions, supplying Test Inputs, interacting with the Candidate Solution, collecting Observations, and restoring or terminating the Test Environment.

A Test Procedure differs from a test script. A Test Procedure specifies the activities and their order independently of the mechanism used to perform them. A test script represents an executable implementation that automates some or all of those activities.

ordered set of activities that implements part or all of a test definition during a test execution

Adapted from the test-process and test-documentation concepts described by:

• ISO/IEC/IEEE 29119-2:2021, Software and systems engineering — Software testing — Part 2: Test processes
• ISO/IEC/IEEE 29119-3:2021, Software and systems engineering — Software testing — Part 3: Test documentation
• ISTQB Glossary, “test procedure”

A Test Procedure identifies or references:

• The applicable Test Definition
• Preconditions
• Required Test Resources
• Required Test Environment
• Test Inputs
• Ordered test activities
• Expected Results
• Observation and Evidence collection activities
• Completion conditions
• Cleanup or restoration activities
• Applicable exception-handling activities

A Test Procedure supports manual execution, automated execution, or a combination of manual and automated execution.

A Test Procedure directs DIDO-TE to:

1. Prepare the designated Test Environment
2. Confirm the Candidate Solution version
3. Supply a Transfer Bundle with a known integrity defect
4. Direct the Candidate Solution to import the Transfer Bundle
5. Record the response and associated log entries
6. Confirm whether deployment activities began
7. Preserve the resulting Observations and Evidence
8. Restore the Test Environment to its required state