| Abstract Test Suite (ATS) |
A test suite composed oftest cases. Typically an ATS is composed of a set ofTTCN-3test casesfor a particular set ofbase standard(s) |
Base Specification
Base Standard
|
A document (usually astandardor technical specification) from a recognized SDO, forum or other organization from whichtest specificationsare 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 particularstandardconforms to the individual requirements of thatstandard. |
| Executable Test Case |
A realization of anabstract test case. |
| Executable Test Suite |
A test suite composed ofexecutable test cases. |
| Fail Verdict |
Atest verdictgiven when the observedtest resulteither demonstrates non-interoperability ofequipment under testwith respect to the end-to-end functionality on which thetest caseis focused, or demonstrates non-conformance with respect to at least one of the conformance requirement(s) on which thetest purpose(s)associated with thetest caseis (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 theImplementation Under Test (IUT). It provides an overview of the features and options that are implemented. The ICS can be used to select and parameterisetest casesand 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 theICS) related to theIUTand its testing environment, which will enable the test laboratory to run an appropriate test suite against theIUT. 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 |
Atest verdictgiven when the observedtest resultis such that neither apassnor afail verdictcan be given. |
| Interoperability Testing (IOT) |
Activity of proving that end-to-end functionality between (at least) two communicating systems is as required by thebase 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 theImplementation 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 atest infrastructureincluding aspects such as addressing plan. |
| Pass Verdict |
Atest verdictgiven when the observedtest resultgives evidence of all equipment under test interoperating for the end-to-end functionality on which thetest caseis focused, or conformance to the conformance requirement(s) on which thetest purpose(s)of thetest caseis (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 thetest 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 theImplementation Under Test (IUT)resides. |
| Test Architecture |
A description ofTTCN-3components and other functional entities as well as their interfaces and connections for a particularsystemorimplementation 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 ofASN.1 |
| Test Bed |
Physical installation of atest infrastructureincluding one or moreSUT(s). |
| Test Campaign |
The process of executing the parameterizedExecutable Test Suitefor a particularIUT. |
| Test Case (TC) |
A complete and independent specification of the actions required to achieve a specifictest purpose. Typically those actions are expressed inTTCN-3. |
| Test Configuration |
A particular concrete instance of atest architecturewhich applies to a set oftest casesand is defined on the basis of test components, ports and their connections. |
Test Description (TD)
Test Scenario, Test Plan
|
An intermediate description between atest purpose(TP)and atest case(TC)in the context ofconformance testing. Ininteroperability testingit is the test itself. |
| Test Framework |
A document providing guidance and examples necessary for the development and implementation of atest 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 theSUT. |
| Test Log |
A human readable record of information produced as a result of atest campaignwhich is sufficient to record the observedtest resultsand to verify the assignment of thetest result(includingtest verdicts). |
| Test Purpose (TP) |
A description in English prose orTPLanof 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 thebase 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 parameterisedexecutable test case. |
| Test Report |
Document that presents thetest resultand other information relevant to a test. |
| Test Specification |
The set of documents for testing thebase standard(s)and/orprofile(s). |
| Test Verdict |
A statement of "pass", "fail" or "inconclusive", specified in anabstract interoperability test case, concerning either the end-to-end interoperability of two or more Equipment Under Test (EUT) or conformance of anImplementation Under Test (IUT)with respect to thattest casewhen it is executed. |
| Upper Tester (UT) |
The means of providing, during test execution, control and observation of the upper service boundary of theImplementation Under Test (IUT), as defined by the chosen Abstract Test Method. |
| Use Case |
Abstract illustration of typical behaviour of a system defined inbase standard(s)and/orprofile(s)usually from a user’s point of view (either human or machine). |
| Validation |
Assessing that abase standard/profileor atest specificationsatisfies an agreed set of criteria. |