scope:

The Abstract Test Suite (ATS) defined by the present document complies with the international standards on conformance testing (ISO 9646-1 [4], ISO 9646-2 [5], ISO 9646-3 [6] and ISO 9646-5 [7]). Results of the joint EWOS/ETSI Project Team No.5 on Open Systems Interconnection (OSI) conformance testing in Europe are also taken into account.

NOTE 1: As defined by ISO 9646, in case of any discrepancy between a base standard and a test suite, the base standard takes precedence above the test suite.

The ATS defined by the present document is applicable to Videotex terminals which make use of the Syntax-based Videotex (SBV) protocol as defined by ETS 300 223 [2] or ETS 300 079 [3].

NOTE 2: The present document does not apply in totality to ETS 300 079 [3] based terminals. As a matter of fact, some services are tested in the present document, which are only defined in ETS 300 223 [2], and not in ETS 300 079 [3]. These services are: SBV_Reset_TC, SBV_End_Immediate, SBV_Remote_Echo. When applying the present document to ETS 300 079 [3] based terminals, the test cases in question should be de-selected.

NOTE 3: At the time of producing the present document, ETS 300 079 [3] contains both the SBV protocol definition and the use of that protocol over an Integrated Services Digital Network (ISDN) DTE/DTE connection. In case of an ETS 300 079 [3] based terminal, tests for layers other than layer 7 are out side the scope of this ETS.

The chosen test method for this ATS ensures that all SBV terminals can be tested without any additional requirement other than those resulting from the protocol standard itself.

NOTE 4: The scope of testing is currently restricted to protocol testing where protocol is understood in the way described in ISO 7498 [16]. Extension of the scope might require other test methods. (See also subclause 5.1 and annex K (informative)).

Test cases are fully specified for those situations in which an SBV terminal acts as a Terminal Function (TF) (see subclause 6.2 of ETS 300 223 [2] or ETS 300 079 [3]).

NOTE 5: This situation, in which the SBV terminal acts as a Terminal Function, covers the following cases: when the communication is established by the terminal itself (without having the reverse_role_assignment parameter present in the Establish PDU), or when the terminal is called by an SBV service or another SBV terminal with this parameter present.

For those situations in which an SBV terminal behaves like an Access Function (AF) (see subclause 6.2 of ETS 300 223 [2] or ETS 300 079 [3]), only the test purposes are given by the present document.

NOTE 6: This situation occurs when a called SBV terminal accepts an incoming Establish request, on which the reverse_role_assignment parameter is not present. This is generally used in case of terminal-to-terminal communication.

NOTE 7: The present document provides only for an empty place-holder for a test case selection table. Completion of this table is left open for the possible transition of the present document to an ETS. As a consequence, and for an interim period, de-selection of those test cases related to optional elements of the base standard needs to be done by other means. It should not be understood that all the test cases are applicable in all cases; a de-selection process is implied.