BS ISO/IEC 9646-3:1998

1 Scope
2 Normative references
3 Definitions
3.1 Basic terms from ISO/IEC 9646-1
3.2 Terms from ISO/IEC 7498-1
3.3 Terms from ISO/IEC 10731
3.4 Terms from ISO/IEC 8824-1
3.5 Terms from ISO/IEC 8825-1
3.6 TTCN specific terms
4 Abbreviations
4.1 Abbreviations defined in ISO/IEC 9646-1
4.2 Abbreviations defined in ISO/IEC 9646-2
4.3 Other abbreviations
5 The syntax forms of TTCN
6 Compliance
7 Conventions
7.1 Introduction
7.2 Syntactic metanotation
7.3 TTCN.GR table proformas
7.4 Free text and bounded free text
8 Concurrency in TTCN
8.1 Test components
8.2 Test component configuration
9 TTCN test suite structure
9.1 Introduction
9.2 Test group references
9.3 Test step group references
9.4 Default group references
9.5 Parts of a TTCN test suite
10 Test suite overview
10.1 Introduction
10.2 Test suite structure
10.3 Test case index
10.4 Test step index
10.5 Default index
10.6 Test suite exports
10.7 The import part
11 Declarations part
11.1 Introduction
11.2 TTCN types
11.3 TTCN operators and TTCN operations
11.4 Test suite parameter declarations
11.5 Test case selection expression definitions
11.6 Test suite constant declarations
11.7 Test suite constant declarations by reference
11.8 TTCN variables
11.9 PCO type declaration
11.10 PCO declaration
11.11 CP declaration
11.12 Timer declarations
11.13 Test components and configuration declarations
11.14 ASP type definitions
11.15 PDU type definitions
11.16 Test suite encoding information
11.17 CM type definitions
11.18 String length specifications
11.19 ASP,PDU and CM definitions for SEND events
11.20 ASP,PDU and CM definitions for RECEIVE events
11.21 Alias definitions
12 Constraints part
12.1 Introduction
12.2 General principles
12.3 Parameterization of constraints
12.4 Chaining of constraints
12.5 Constraints for SEND events
12.6 Constraints for RECEIVE events
13 Specification of constraints using tables
13.1 Introduction
13.2 Structured type constraint declarations
13.3 ASP constraint declarations
13.4 PDU constraint declarations
13.5 Parameterization of constraints
13.6 Base constraints and modified constraints
13.7 Formal parameter lists in modified constraints
13.8 CM constraints declarations
14 Specification of constraints using ASN.1
14.1 Introduction
14.2 ASN.1 type constraint declarations
14.3 ASN.1 ASP constraint declarations
14.4 ASN.1 PDU constraint declarations
14.5 Parameterized ASN.1 constraints
14.6 Modified ASN.1 constraints
14.7 Formal parameter lists in modified ASN.1 constraints
14.8 ASP parameter and PDU field names within ASN.1 constraints
14.9 ASN.1 CM constraint declarations
15 The dynamic part
15.1 Introduction
15.2 Test case dynamic behaviour
15.3 Test step dynamic behaviour
15.4 Default dynamic behaviour
15.5 The behaviour descriptions
15.6 The tree notation
15.7 Tree names and parameter lists
15.8 TTCN statements
15.9 TTCN test events
15.10 TTCN expressions
15.11 Pseudo-events
15.12 Timer management
15.13 The ATTACH construct
15.14 Labels and the GOTO construct
15.15 The REPEAT construct
15.16 The constraints reference
15.17 Verdicts
15.18 The meaning of defaults
16 Page continuation
16.1 Page continuation of TTCN tables
16.2 Page continuation of dynamic behaviour tables
A (normative)
A.1 Introduction
A.2 Conventions for the syntax description
A.3 The TTCN.MP syntax productions in BNF
A.4 General static semantics requirements
A.5 Differences in syntax
A.6 List of BNF production numbers
B (normative)
B.1 Introduction
B.2 Precedence
B.3 Processing of test case errors
B.4 Converting a modularized test suite to an equivalent expanded
     test suite
B.5 TTCN operational semantics
C (normative)
C.1 Introduction
C.2 TTCN module overview part
C.3 Import part
D (normative)
D.1 Introduction
D.2 The test suite index
E (normative)
E.1 Introduction
E.2 Compact proformas for constraints
E.3 Compact proforma for test cases
F (informative)
F.1 Examples of tabular constraints
F.2 Examples of ASN1 constraints
F.3 Base and modified constraints
F.4 Type definition using macros
F.5 Use of REPEAT
F.6 Test suite operations
F.7 Example of a test suite overview
F.8 Example of a test case in TTCB.MP form
F.9 Use of component reference for field value assignment in constraints
F.10 Multi-party testing
F.11 Multiplexing/demultiplexing
F.12 Splitting and recombing
F.13 Multi-protocol test cases
F.14 Example of modular TTCN
F.15 Example of CREATE and DONE
G (informative) Style guide
G.1 Introduction
G.2 Test case structure
G.3 Use of TTCN with different abstract test methods
G.4 Use of defaults
G.5 Limiting the execution time of a test case
G.6 Structured types
G.7 Abbreviations
G.8 Test descriptions
G.9 Assignments of SEND events
G.10 Multi-service PCOs
H (informative)
H.1 Introduction
H.2 The index

Notation (TTCN), for OSI conformance test suites. Reflects the abstract testing methodology defined in ISO/IEC 9646-1 and ISO/IEC 9646-2. Coverage includes definitions, abbreviations and compliance. Also includes detailed annexes.

1.1 This part of ISO/IEC9646 defines an informal test notation, called the Tree and Tabular Combined Notation (TTCN), for OSI conformance test suites, which is independent of test methods, layers and protocols, and which reflects the abstract testing methodology defined in ISO/IEC9646-1 and ISO/IEC9646-2. 1.2 It also specifies requirements and provides guidance for using TTCN in the specification of system-independent conform-ance test suites for one or more OSI standards. It specifies two forms of the notation: one, a human-readable form, applicable to the production of conformance test suite standards for OSI protocols; and the other, a machine-processable form, applicable to processing within and between computer systems. 1.3 This part of ISO/IEC9646 applies to the specification of conformance test cases which can be expressed abstractly in terms of control and observation of protocol data units and abstract service primitives. Nevertheless, for some protocols, test cases may be needed which cannot be expressed in these terms. The specification of such test cases is outside the scope of this part of ISO/IEC9646, although those test cases may need to be included in a conformance test suite standard. For example, some static conformance requirements related to an application service may require testing techniques which are specific to that particular application. The specification of test cases in which more than one behaviour description is to be run in parallel is dealt with by the concurrency features (particularly involving the definition of Test Components and Test Component Configurations). 1.4 This part of ISO/IEC9646 specifies requirements on what a test suite standard may specify about a conforming realization of the test suite, including the operational semantics of TTCN test suites. 1.5 This part of ISO/IEC9646 applies to the specification of conformance test suites for OSI protocols in OSI layers 2 to 7, specifically including Abstract Syntax Notation One (ASN.1) based protocols. The following are outside the scope of this part of ISO/IEC9646: the specification of conformance test suites for Physical layer protocols; the relationship between TTCN and formal description techniques; the means of realization of executable test suites (ETS) from abstract test suites. 1.6 This part of ISO/IEC9646 defines mechanisms for using concurrency in the specification of abstract test cases. Concurrency in TTCN is applicable to the specification of test cases: in a multi-party testing context; which handle multiplexing and demultiplexing in either a single-party or multi-party testing context; which handle splitting and recombining in either a single-party or multi-party testing context; in a single-party testing context when the complexity of the protocol or set of protocols handled by the IUT is such that concurrency can simplify the specification of the test case. 1.7 TTCN modules are defined to allow sharing of common TTCN specifications between test suites.