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_resource [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:t:test_resource [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Test Resource ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Test Resource supports the preparation, | ||
| + | |||
| + | Test Resources include physical and digital assets such as: | ||
| + | |||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * Test datasets | ||
| + | * Test scripts and procedures | ||
| + | * Expected results and evaluation criteria | ||
| + | * Configuration and deployment artifacts | ||
| + | * Software tools, simulators, emulators, and instrumentation | ||
| + | * [[public: | ||
| + | * Templates and reference implementations | ||
| + | * Hardware used for testing | ||
| + | |||
| + | A Test Resource differs from a [[public: | ||
| + | |||
| + | A Test Resource also differs from a [[public: | ||
| + | |||
| + | A Test Resource does not inherently qualify as reusable. [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //physical or digital asset used to prepare, execute, evaluate, or report testing// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Adapted from the testing and testware concepts defined by: | ||
| + | |||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | The term **Test Resource** has a broader scope than **testware**. Testware consists of work products produced during the test process. Test Resources also include acquired assets, physical equipment, infrastructure components, tools, simulators, reference materials, and other assets that support testing. | ||
| + | |||
| + | An asset produced during testing, including an [[public: | ||
| + | |||
| + | A Test Resource description identifies or references: | ||
| + | |||
| + | * A persistent identifier | ||
| + | * Purpose | ||
| + | * Resource type | ||
| + | * Version | ||
| + | * Supported uses | ||
| + | * Applicable constraints | ||
| + | * [[public: | ||
| + | * Compatibility conditions | ||
| + | * Provenance | ||
| + | * Integrity information | ||
| + | * Maintenance status | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | DIDO-TE maintains a test script, a signed Transfer Bundle containing known integrity defects, and the associated expected results. These assets constitute Test Resources because they support the execution and evaluation of integrity-validation tests against Candidate Solutions. | ||
| + | |||
| + | DIDO-TE designates the resources as reusable after recording their versions, dependencies, | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||