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 [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:t:test [2026/09/13 17:06] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Test ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A **Test** is the general testing concept used to evaluate one or more characteristics of a subject under defined conditions. | ||
| + | |||
| + | The term is intentionally broader than more specialized testing concepts such as [[public: | ||
| + | |||
| + | A Test may be described, organized, or realized using one or more of those concepts, but it is not synonymous with any one of them. | ||
| + | |||
| + | The Test Information Interchange Format (TestIF) intentionally provides foundational testing concepts that can support differing organizational, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | //A governed specification or activity used to evaluate one or more characteristics of a Test Object under defined conditions and to determine whether observed results satisfy applicable Expected Results, criteria, or requirements.// | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | * Object Management Group, Test Information Interchange Format (TestIF) 1.0 | ||
| + | * [[private: | ||
| + | * DIDO-TE architectural normalization | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Test may include or reference: | ||
| + | |||
| + | * the subject or [[public: | ||
| + | * applicable [[public: | ||
| + | * defined test conditions | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * the [[public: | ||
| + | * [[public: | ||
| + | * supporting [[public: | ||
| + | |||
| + | The exact internal structure of a Test depends on the applicable testing model, profile, policy, or Test Definition. | ||
| + | |||
| + | A Test is distinct from a [[public: | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Test may specify that a candidate Node implementation is evaluated for conformance with a governed protocol requirement under defined network conditions. | ||
| + | |||
| + | The Test may identify: | ||
| + | |||
| + | * the Node as the Test Object | ||
| + | * one or more Test Cases | ||
| + | * applicable Test Executables | ||
| + | * the required Test Environment | ||
| + | * Expected Results | ||
| + | * Validation Criteria | ||
| + | |||
| + | One or more Test Runs may subsequently execute that Test. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||