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_purpose [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:t:test_purpose [2026/09/13 17:06] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Test Purpose ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A **Test Purpose** identifies why a [[public: | ||
| + | |||
| + | The concept is aligned with the Test Information Interchange Format (TestIF), where Test Purpose provides a textual description of the reason for a test. | ||
| + | |||
| + | Within DIDO-TE, Test Purpose provides the semantic rationale for conducting testing and may be used to organize, select, govern, or interpret related Test Objects. | ||
| + | |||
| + | A Test Purpose is distinct from: | ||
| + | |||
| + | * a test objective, which may state a specific measurable outcome | ||
| + | * a [[public: | ||
| + | * [[public: | ||
| + | * a [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //The reason for performing a Test or grouping related Test Objects.// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * Object Management Group, Test Information Interchange Format (TestIF) 1.0, '' | ||
| + | * [[private: | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Test Purpose describes the intended reason or motivation for testing rather than the procedure used to perform the Test. | ||
| + | |||
| + | Examples of Test Purposes may include: | ||
| + | |||
| + | * demonstrating conformance with a specified requirement | ||
| + | * evaluating interoperability between implementations | ||
| + | * determining whether a Node behaves correctly under a defined network condition | ||
| + | * evaluating performance under a specified workload | ||
| + | * verifying behavior following a state transition | ||
| + | * comparing two candidate implementations | ||
| + | |||
| + | A single Test Purpose may be associated with multiple Test Objects. | ||
| + | |||
| + | A [[public: | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | For a Test Set containing Test Cases that evaluate Node behavior following loss and restoration of network connectivity, | ||
| + | |||
| + | > | ||
| + | |||
| + | The individual Test Cases define specific conditions and actions used to evaluate that purpose. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||