Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:t:test_procedure [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:t:test_procedure [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Test Procedure ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Test Procedure specifies the ordered activities that implement part or all of a [[public: | ||
| + | |||
| + | The Test Procedure translates the intent and conditions of the Test Definition into executable activities. These activities include preparing the [[public: | ||
| + | |||
| + | 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. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //ordered set of activities that implements part or all of a test definition during a test execution// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from the test-process and test-documentation concepts described by: | ||
| + | |||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | 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. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Test Procedure directs DIDO-TE to: | ||
| + | |||
| + | - Prepare the designated Test Environment | ||
| + | - Confirm the Candidate Solution version | ||
| + | - Supply a Transfer Bundle with a known integrity defect | ||
| + | - Direct the Candidate Solution to import the Transfer Bundle | ||
| + | - Record the response and associated log entries | ||
| + | - Confirm whether deployment activities began | ||
| + | - Preserve the resulting Observations and Evidence | ||
| + | - Restore the Test Environment to its required state | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||