This section provides an explanation of frequently used terms from the Testing Domain. If you wish to add further terms please contact cti@etsi.org. For the strict definitions of the terms please refer to the following sources:
| Abstract Test Suite (ATS) | A test suite composed of test cases. Typically an ATS is composed of a set of TTCN-3 test cases for a particular set of base standard(s) |
| Base Specification
Base Standard
|
A document (usually a standard or technical specification) from a recognized SDO, forum or other organization from which test specifications are derived. Typically these will be applications, services or protocols (including abstract syntax, encoding rules or information objects). |
| Conformance Testing
Compliance Testing, Conformity Testing
|
Activity of testing to determine to what extent an implementation of a particular standard conforms to the individual requirements of that standard. |
| Executable Test Case | A realization of an abstract test case. |
| Executable Test Suite | A test suite composed of executable test cases. |
| Fail Verdict | A test verdict given when the observed test result either demonstrates non-interoperability of equipment under test with respect to the end-to-end functionality on which the test case is focused, or demonstrates non-conformance with respect to at least one of the conformance requirement(s) on which the test purpose(s) associated with the test case is (are) focused, or contains at least one invalid test event, with respect to the relevant specifications. |
| Implementation Conformance Statement (ICS) | The Implementation Conformance Statement (ICS) is a checklist of the capabilities supported by the Implementation Under Test (IUT). It provides an overview of the features and options that are implemented. The ICS can be used to select and parameterise test cases and as an indicator for basic interoperability between different products. In the case of protocols, the ICS can take several forms: Protocol ICS, Profile ICS, Profile Specific ICS. |
| Implementation eXtra Information for Testing (IXIT) | The Implementation eXtra Information for Testing (IXIT) is a checklist which contains or references all of the information (in addition to that given in the ICS) related to the IUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the IUT. In the case of protocols, the IXIT can take several forms: Protocol IXIT, Profile IXIT, Profile Specific IXIT. |
| Implementation Under Test (IUT) | That part of a real system which is to be tested, which should be an implementation of applications, services or protocols. |
| Inconclusive Verdict | A test verdict given when the observed test result is such that neither a pass nor a fail verdict can be given. |
| Interoperability Testing (IOT) | Activity of proving that end-to-end functionality between (at least) two communicating systems is as required by the base standard(s) on which those systems are based. |
| Lower tester (LT) | The means of providing, during test execution, indirect control and observation of the lower service boundary of the
Implementation Under Test (IUT) via the underlying service provider. NOTE: The underlying service-provider is immediately beneath the (lowest layer) protocol which is the focus of testing. It may use one or more OSI layers, or only the physical medium. |
| Network Topology
Topology Map
|
Illustration of a test infrastructure including aspects such as addressing plan. |
| Pass Verdict | A test verdict given when the observed test result gives evidence of all equipment under test interoperating for the end-to-end functionality on which the test case is focused, or conformance to the conformance requirement(s) on which the test purpose(s) of the test case is (are) focused, and when all the test events are valid with respect to the relevant specifications. |
| Protocol Profile
Profile
|
A document which specifies a selection of options from one or more related protocols, possibly together with one or more transfer syntaxes and/or information objects. |
| Point of Control and Observation (PCO) | A point within a testing environment where the occurrence of test events is to be controlled and observed, as defined in the
test architecture. "NOTE: A PCO is characterized by the set of Abstract Service Primitives (ASPs) and/or Protocol Data Units (PDUs) that can occur. |
| Standard | Document, established by consensus and approved by a recognized body, that provides, for common and repeated use, rules, guidelines or characteristics for activities or their results, aimed at the achievement of the optimum degree of order in a given context. Standards should be based on the consolidated results of science, technology and experience, and aimed at the promotion of optimum community benefits. |
| System under test (SUT) | The real system in which the Implementation Under Test (IUT) resides. |
| Test Architecture | A description of TTCN-3 components and other functional entities as well as their interfaces and connections for a particular system or implementation under test. |
| Tabular Encoding | Look-up table defining bit positions and encoding. NOTE: Tabular encoding is a form of manual encoding which is contrary to automatic encoding forms such as the usage of ASN.1 |
| Test Bed | Physical installation of a test infrastructure including one or more SUT(s). |
| Test Campaign | The process of executing the parameterized Executable Test Suite for a particular IUT. |
| Test Case (TC) | A complete and independent specification of the actions required to achieve a specific test purpose. Typically those actions are expressed in TTCN-3. |
| Test Configuration | A particular concrete instance of a test architecture which applies to a set of test cases and is defined on the basis of test components, ports and their connections. |
| Test Description (TD)
Test Scenario, Test Plan
|
An intermediate description between a test purpose(TP) and a test case(TC) in the context of conformance testing. In interoperability testing it is the test itself. |
| Test Framework | A document providing guidance and examples necessary for the development and implementation of a test specification. |
| Test Infrastructure | The basic physical structure necessary to facilitate a testing activity, such as the provision of an underlying network, trace capture tools, analysers, reporting tools, power etc. but not including the SUT. |
| Test Log | A human readable record of information produced as a result of a test campaign which is sufficient to record the observed test results and to verify the assignment of the test result (including test verdicts). |
| Test Purpose (TP) | A description in English prose or TPLan of a well defined objective of testing, focusing on either a specific end-to-end functionality, a single conformance requirement or a set of related conformance requirements as specified in the base specification (e.g. verifying the support of a specific value of a specific parameter). |
| Test Result
Test Outcome
|
The sequence of test events, together with associated data and/or parameter values, which occurred during test execution of a specific parameterised executable test case. |
| Test Report | Document that presents the test result and other information relevant to a test. |
| Test Specification | The set of documents for testing the base standard(s) and/or profile(s). |
| Test Verdict | A statement of "pass", "fail" or "inconclusive", specified in an abstract interoperability test case, concerning either the end-to-end interoperability of two or more Equipment Under Test (EUT) or conformance of an Implementation Under Test (IUT) with respect to that test case when it is executed. |
| Upper Tester (UT) | The means of providing, during test execution, control and observation of the upper service boundary of the Implementation Under Test (IUT), as defined by the chosen Abstract Test Method. |
| Use Case | Abstract illustration of typical behaviour of a system defined in base standard(s) and/or profile(s) usually from a user’s point of view (either human or machine). |
| Validation | Assessing that a base standard/profile or a test specification satisfies an agreed set of criteria. |