Testing and Modeling With TDL

TESTING AND MODELING WITH TDL
Philip Makedonski, Gusztav Adamis, Martti Käärik,

Finn Kristoffersen, Andreas Ulrich, Xavier Zeitoun
Overview
What is TDL?
Why TDL?
• Test Description Language
Final draft ETSI ES 203 119-1 V1.2.0 (2015-04)
• Design, documentation, and • For users

representation of formal test ETSI STANDARD • separate test specification from test implementation
descriptions Methods for Testing and Specification (MTS);
The Test Description Language (TDL);
• amenable to tool-supported verification ETSI ES 203
Part 1: Abstract Syntax and Associated Semantics ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
9-2) V1.2.1
• Scenario-based approach • adjustable to stakeholders

3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
• Standardised at ETSI by TC MTS

ETSI STAND
ARD
• focus on what to test vs how

ETSI STA
NDARD
ETSI STANDARD
Methods for
ETSI STANDARD Testin
The Test Desc g and Specification
Met
Part 4: Struc hod s for Tes
ription Lang (MTS);
Methodstured
The
for Testing ting
andand uage
Specification (MTS);
Test
Tes Objec
t Des Specific(TDL) ;
criptive
The Test Description Spec
Language TS);
atio
ificati
TestingPar
forAbstract and tion
Specific
t 2: Langua (TDL);
ation(M on n(Exte
(MTnsion
S); )
Parts 1: (TDL); geSemantics
• For tool vendors

Method Syntax Gra
and Associated
geal
phic (TDL);
• STF 454 (2013)

tion Langua Syntax
The Test Descrip Format
Part 3: Exchange
• STF 476 (2014) • universal standardised exchange format

• STF 492 (2015) Where does TDL fit in?
!
• support for customers from different domains !
• reuse of and integration with existing tools
3 Keyword-Driven• focus on core expertise, add value through interoperability

Testing
X
MBT Final draft ETSI ES 203

Representation
Rail
ETSI ES 119-4 V1.1.0 (2015-04)
Final draft
Final draft ETSI ES 203 119-1
203 119 V1.2.0 (2015-04)
Generation
ES 203 119-3 V1.1.0 -2 V1.1.0 (2015-0
(2015-04)
Final draft ETSI 4)
ETSI STANDARD
ETSI STANDA
RD
ETSI STANDARD
Methods for
ETSI STANDARD Testing and
The Test Descriptio
Method Specificati
Part 4: Structured s for Testingn Language on (MTS);
MethodsTheforTest
Testing
Test andand
Objective Specifi (TDL);
Descrip Specificati
cation
The Test Description
Part 2: Language
tion Langua (TDL);
on (Extension
(MTS);
Part 1: Abstract Syntax Graphi
and Associated ge (TDL); )
cal Syntax Semantics
(MTS);
and Specification
Methods for Testing Language (TDL);
The Test Description Format
Part 3: Exchange
Standards !
Visualisation
Documentation ITS
Interoperability Conformance
46
2
What is TDL?

ETSI ES 203 119-1 V1.3.1 (2016-09)
• Design, documentation, and

representation of formalised test ETSI STANDARD
descriptions Methods for Testing and Specification (MTS);

Part 1: Abstract Syntax and Associated Semantics
• Scenario-based approach
• STF 454 (2013)
• STF 476 (2014)
!
• STF 492 (2015)
3
What is TDL?
• Design, documentation,
ETSI ES 203 119-1 V1.3.1 (2016-09)
representation?
• ease development and review ETSI STANDARD
• improve productivity and quality Methods for Testing and Specification (MTS);
• both industry and standardisation

• reduce implementation details
4
MBT Workflow Manual Workflow
System Requirements Specification Requirements Level
Model TPLan TDL-TO
Test Generator Test Design Level
TDL
Test Code Generator
TTCN-3 (or Other Execution Language) Test Implementation Level
Adaptation
Executable Tests Test Execution Level
5
What is TDL?
• Scenario-based?
ETSI ES 203 119-1 V1.3.1 (2016-09)
• describe interactions with a system

• attach test objectives to scenarios ETSI STANDARD
• derive and automate tests Methods for Testing and Specification (MTS);
• Reactive, distributed, real-time

• common black-box testing concepts
• domain adaptation
• agile development !
6
What is TDL?
• Standardised?
ETSI ES 203 119-1 V1.3.1 (2016-09)
• canonical reference
• stable documentation ETSI STANDARD
• clear semantics Methods for Testing and Specification (MTS);

• interoperability and independence

• updated with user needs
• maintenance commitment
!
7
What is TDL?
• Contributions from:
ETSI ES 203 119-1 V1.3.1 (2016-09)
• Siemens AG, Ericsson Hungary

• Fraunhofer FOKUS, ETSI CTI ETSI STANDARD
• CEA, University of Göttingen Methods for Testing and Specification (MTS);

• OU Elvior, Cinderella ApS

• Guidance:
• Steering Group, TC MTS
!
8
What is TDL?
ETSI ES 203 119-2 V1.2.1 (2016-09)
Part 2: GR
ETSI STANDARD Graphical
Methods for Testing and Specification (MTS);
Syntax
Part 2: Graphical Syntax
ETSI ES 203 119-1 V1.3.1 (2016-09) ETSI ES 203 119-3 V1.2.1 (2016-09)
Part 3: XF
Part 1: MM ETSI STANDARD ETSI STANDARD Exchange
Meta-Model Methods for Testing and Specification (MTS); Methods for Testing and Specification(MTS);
Format
and Semantics
The Test Description Language (TDL); The Test Description Language (TDL);
Part 1: Abstract Syntax and Associated Semantics Part 3: Exchange Format
ETSI ES 203 119-4 V1.2.1 (2016-09)
Part 4: TO
ETSI STANDARD Structured
Test Objective
Specification
!
Part 4: Structured Test Objective Specification (Extension)
9
What is TDL?
ETSI ES 203 119-1 V1.3.1 (2016-09)
ETSI STANDARD

User-defined syntax
!
ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
TDL P2: GR
TDL P4: TO
TDL P3: XF
ETSI ES 203 119-3 V1.2.1 (2016-09)
ETSI STANDARD
Methods for Testing and Specification(MTS);

Part 3: Exchange Format
TDL P1: MM
ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

10
What is TDL?
ETSI ES 203 119-1 V1.3.1 (2016-09)
ETSI STANDARD

User-defined syntax
!
ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
TDL P2: GR
TDL P4: TO
TDL P3: XF
ETSI ES 203 119-3 V1.2.1 (2016-09)
ETSI STANDARD

TDL P1: MM
ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

11
Semantics
What is TDL? A 'GateType' represents a type of communication points, called

'ComponentInstance's. A 'GateType' specifies the 'DataType's th
both directions.
ETSI ES 203 119-1 V1.3.1 (2016-09)
Generalization
ETSI STANDARD
• PackageableElement Methods for Testing and Specification (MTS);

User-defined syntax
Properties !
• dataType: DataType [1..*] {unique}

ETSI ES 203 119-2 V1.2.1 (2016-09)
The 'DataType's that can be exchanged via 'GateInstan

ETSI STANDARD
TDL P2: GR
TDL P4: TO
TDL P3: XF
shall adhere to the 'DataType's that are allowed to be e
Constraints
There are no constraints specified. ETSI ES 203 119-3 V1.2.1 (2016-09)
ETSI STANDARD
8.2.2 GateInstance
Semantics
TDLAP1: MM
ETSI ES 203 119-4 V1.2.1 (2016-09)
'GateInstance' represents an instance of a 'GateType'. It is the

'ComponentInstance's. A 'GateInstance' is contained in a 'Comp
ETSI STANDARD

Generalization
• NamedElement
12
Into the lower empty compartment the elements of the TestCon
6.4.2 GateType
What is TDL? Concrete Graphical Notation
! " # $ ETSI ES 203 119-1 V1.3.1 (2016-09)
!"#"$%&'()%& " $ $ ETSI STANDARD

Formal Description
User-defined syntax
!
ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
TDL P2: GR
TDL P4: TO
TDL P3: XF
Comments
No comments. ETSI ES 203 119-3 V1.2.1 (2016-09)
ETSI STANDARD

TDL P1: MM
ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD
ETSI
Radio
Data Type: Message, Signal
13
What is TDL? Part 1: MM
• TDL main ingredients

ETSI ES 203 119-1 V1.3.1 (2016-09)
• Test data
• Test configuration ETSI STANDARD
ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
• Test behaviour Methods for Testing and Specification (MTS); Methods for Testing and Specification (MTS);

• Test objectives
ETSI ES 203 119-3 V1.2.1 (2016-09)
• Time ETSI STANDARD

ETSI ES 203 119-4 V1.2.1 (2016-09)

!
ETSI STANDARD

14

ETSI ES 203 119-1 V1.3.1 (2016-09) 54 ETSI ES 203 119 V1.1.1 (2014-04)
Annex B (informative):
Examples of a TDL Concrete Syntax
• Test data
B.1 Introduction
The applicability of the TDL meta-model that is described in the main part of the present document depends on the
availability of TDL concrete syntaxes that implement the meta-model (abstract syntax). Such a TDL concrete syntax
can then be used by end users to write TDL specifications. Though a concrete syntax will be based on the TDL meta-
model, it can implement only parts of the meta-model if certain TDL features are not necessary to handle a user's needs.
This annex illustrates an example of a possible TDL concrete syntax in a textual format that supports all features of the
• Test configuration
TDL meta-model, called "TDLan". Three examples are outlined below - two examples translated from existing test
descriptions taken from [i.2] and [i.3], as well as an example illustrating some of the TDL data parameterization and
mapping concepts. The examples are accompanied by a complete reference description of the textual syntax of TDLan ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
given in EBNF.
B.2 A 3GPP Conformance Example in Textual Syntax ETSI STANDARD
• Test behaviour
This example describes one possible way to translate clause 7.1.3.1 from TS 136 523-1 [i.2] into the proposed TDL
textual syntax, by mapping the concepts from the representation in the source document to the corresponding concepts
in the TDL meta-model by means of the proposed textual syntax. The example has been enriched with additional Part 2: Graphical Syntax

information, such as explicit data definitions and test configuration details for completeness where applicable.
Part
//Translated from1: Abstract
[i.2], Syntax and Associated Semantics
Section 7.1.3.1
TDLan Specification Layer_2_DL_SCH_Data_Transfer {
//Procedures carried out by a component of a test configuration
//or an actor during test execution
• Test objectives
Action preCondition : "Pre-test Conditions:
RRC Connection Reconfiguration" ;
Action preamble : "Preamble:
The generic procedure to get UE in test state Loopback
Activated (State 4) according to TS 36.508 clause 4.5
is executed, with all the parameters as specified in the
procedure except that the RLC SDU size is set to return no
data in uplink.
(reference corresponding behaviour once implemented" ;
//User-defined verdicts
ETSI ES 203 119-3 V1.2.1 (2016-09)
• Time
//Alternatively the predefined verdicts may be used as well
Verdict PASS ;
Verdict FAIL ;
//User-defined annotation types

Annotation TITLE ; //Test description title
Annotation STEP ; //Step identifiers in source documents ETSI STANDARD
Annotation PROCEDURE ; //Informal textual description of a test step

Annotation PRECONDITION ; //Identify pre-condition behaviour
Annotation PREAMBLE ; //Identify preamble behaviour. The Test Description Language (TDL);
//User-defined time units

Time Unit seconds;
//Test objectives (copied verbatim from source document)

Test Objective TP1 {
from : "36523-1-a20_s07_01.doc::7.1.3.1.1 (1)" ;
description : "with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives downlink assignment on the PDCCH
for the UE's C-RNTI and receives data in the
associated subframe and UE performs HARQ
operation }
then { UE sends a HARQ feedback on the HARQ
process }
}" ;
}
ETSI ES 203 119-4 V1.2.1 (2016-09)
!
ETSI
ETSI STANDARD

15
What is TDL? Part 1: MM ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI ES 203 119-1 V1.3.1 (2016-09) 54 ETSI ES 203 119 V1.1.1 (2014-04)
ETSI STANDARD
• Test data
B.1 Introduction The Test Description Language (TDL);
mapping concepts. The examples are accompanied by a complete reference description of the textual syntax of TDLan
ETSI STANDARD
given in EBNF.
B.2 A 3GPP Conformance Example in Textual Syntax
• Test behaviour
in the TDL meta-model by means of the proposed textual syntax. The example has been enriched with additional
Part
Section 7.1.3.1
• Test objectives
data in uplink.
ETSI ES 203 119-3 V1.2.1 (2016-09)
• Time
Verdict PASS ;
Verdict FAIL ;



Time Unit seconds;

from : "36523-1-a20_s07_01.doc::7.1.3.1.1 (1)" ;
ensure that {
operation }
process }
}" ;
}
ETSI ES 203 119-4 V1.2.1 (2016-09)
!
ETSI
ETSI STANDARD

16

ETSI ES 203 119-1 V1.3.1 (2016-09) 54 ETSI ES 203 119 V1.1.1 (2014-04)
• Test data
B.1 Introduction
mapping concepts. The examples are accompanied by a complete reference description of the textual syntax of TDLan ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
given in EBNF.
B.2 A 3GPP Conformance Example in Textual Syntax ETSI STANDARD
• Test behaviour
in the TDL meta-model by means of the proposed textual syntax. The example has been enriched with additional Part 2: Graphical Syntax

Part
Section 7.1.3.1
• Test objectives
data in uplink.
ETSI ES 203 119-3 V1.2.1 (2016-09)
• Time
Verdict PASS ;
Verdict FAIL ;



Time Unit seconds;

from : "36523-1-a20_s07_01.doc::7.1.3.1.1 (1)" ;
ensure that {
operation }
process }
}" ;
}
ETSI ES 203 119-4 V1.2.1 (2016-09)
!
ETSI
ETSI STANDARD

17
• Test data
ETSI ES 203 119-1 V1.3.1 (2016-09)
• data definition and data use

• abstract types and instances ETSI STANDARD
ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
• composed by using parameters Methods for Testing and Specification (MTS); Methods for Testing and Specification (MTS);

• functions and actions

ETSI ES 203 119-3 V1.2.1 (2016-09)
• mappable to concrete data ETSI STANDARD

• variables and special values

ETSI ES 203 119-4 V1.2.1 (2016-09)
!
ETSI STANDARD

18
ET
Type Login; Test Design
Login correct;
Login incorrect;
Use "data.ttcn3" as DATA ; ETSI STAND
Map correct to "johnny_correct" in DATA as correct_ttcn3;

Map incorrect to "johnny_incorrect" in DATA as incorrect_ttcn3;
Pa
template Login johnny_correct := { type record Login { Test Implementation

user := "johnny", charstring user,
password := "apple", charstring password,
hint := "seed", charstring hint,
id := 1000 integer id
} } with {
template Login johnny_incorrect := { encode "xpath=//div[@id='login']"; !
user := "johnny", encode (user) "relative=/div/dd[3]";
password := "orange", encode (password) "relative=/div/dd[4]";
hint := "second favourite fruit", };
id := 2000
}
19
ET
Type Login;
Login correct;
Login incorrect;

Pa
20
ET
Type Login;
Login correct;
Login incorrect;

Pa
21
ETSI ES 203 119-1 V1.3.1 (2016-09)
• typed components and gates

• timers and variables ETSI STANDARD
• connections among gates Methods for Testing and Specification (MTS);

• component roles
22
ET
Gate Type gt accepts Login, Response;
Component Type ct having {

gate g of type gt;
} ETSI STAND
Test Configuration tc {
create Tester tester of type ct;
Pa
create SUT sut of type ct;
connect tester.g to sut.g;
}
23
• Test behaviour
ETSI ES 203 119-1 V1.3.1 (2016-09)
• defines expected behaviour

• failure upon deviations by default ETSI STANDARD
• actions and interactions Methods for Testing and Specification (MTS);

• alternative, parallel, iterative,

conditional
• defaulting, interrupting, breaking
24
ET
Test Description td (p of type Login)
uses configuration tc {
tester.g sends incorrect to sut.g;
alternatively {
sut.g sends failure to tester.g with { ETSI STAND
test objectives : tp;
};
set verdict to pass;
Pa
} or {
sut.g sends success to tester.g;
set verdict to fail;
}
}
or simply (relying on the default semantics):

Test Description td_default (p of type Login)
uses configuration tc { !
tester.g sends incorrect to sut.g;

sut.g sends failure to tester.g with {
};
}
25
• Test objectives
ETSI ES 203 119-1 V1.3.1 (2016-09)
• may be attached to
• behaviour (atomic or compound) ETSI STANDARD
• whole test description Methods for Testing and Specification (MTS);

• contain description and reference
26
ET
Test Objective tp {
description : "ensure that
when incorrect login is provided
a failure response is sent";
}
ETSI STAND
Test Description td (p of type Login)
uses configuration tc {
tester.g sends incorrect to sut.g; Pa
alternatively {
sut.g sends failure to tester.g with {
};
set verdict to pass;
} or {
sut.g sends success to tester.g;
set verdict to fail;
}
} !
27
What is TDL? Part 2: GR
ETSI ES 203 119-1 V1.3.1 (2016-09)
• Graphical languages
ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD

• common in (test) modelling

!
• ease communication ETSI STANDARD
• TDL Graphical Syntax Methods for Testing and Specification (MTS);

• hybrid graphical language ETSI ES 203 119-3 V1.2.1 (2016-09)
• simple shapes, compartments ETSI STANDARD

• textual visualisation of contents

ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

28
ETSI ES 203 119-1 V1.3.1 (2016-09)
• Aligned with UML

ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD

• distinct where semantics differ

!
• One diagram to rule them all! ETSI STANDARD
• BNF-like label specification

• Considers both ease of use   ETSI ES 203 119-3 V1.2.1 (2016-09)
and implementation ETSI STANDARD

• Prototyped with Sirius

ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

29
ETSI ES 203 119-1 V1.3.1 (2016-09)
ETSI ES 203 119-2 V1.2.1 (2016-09)

COMPONENTTYPELABEL ETSI STANDARD

timer: TIMERLISTLABEL
!
ETSI STANDARD
GATELABEL
context: ComponentType The Test Description Language (TDL);
COMPONENTTYPELABEL ::= self.name

TIMERLISTLABEL ::= self.timer.name ETSI ES 203 119-3 V1.2.1 (2016-09)
…
ETSI STANDARD

ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

30
ETSI ES 203 119-1 V1.3.1 (2016-09)
ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI STANDARD

ETSI STANDARD

ETSI ES 203 119-3 V1.2.1 (2016-09)
ETSI STANDARD

ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

31
What is TDL? Part 3: XF
ETSI ES 203 119-1 V1.3.1 (2016-09)
• Based on OMG XMI

ETSI ES 203 119-3 V1.2.1 (2016-09)
ETSI STANDARD

• XML: Metadata Interchange

!
• Serialisation of MOF models ETSI STANDARD

ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
• Exchange among MOF tools Methods for Testing and Specification(MTS); Methods for Testing and Specification (MTS);

• XMI concerns
• complex, many options
ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

32
ETSI ES 203 119-1 V1.3.1 (2016-09)
• TDL specific XMI structure

ETSI ES 203 119-3 V1.2.1 (2016-09)
ETSI STANDARD

• exchange of TDL models

!
• canonical TDL XMI structure ETSI STANDARD

ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
• meta-class representations Methods for Testing and Specification(MTS);

• multiplicity, associations, inheritance

• restrict flexibility of XMI
• syntactical validity only!
ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

33
ETSI ES 203 119-1 V1.3.1 (2016-09)
• Syntactical validity only?

ETSI ES 203 119-3 V1.2.1 (2016-09)
ETSI STANDARD

• two-step validation
!
• syntax: XMI Schema ETSI STANDARD

ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
• semantics: MOF model validation Methods for Testing and Specification(MTS); Methods for Testing and Specification (MTS);

ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

34
ETSI ES 203 119-1 V1.3.1 (2016-09)
ETSI ES 203 119-3 V1.2.1 (2016-09)

ETSI STANDARD

ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI STANDARD
ETSI STANDARD
Methods for Testing and Specification(MTS); Methods for Testing and Specification (MTS);

<xsd:complexType name="ComponentInstance">
<xsd:complexContent>
<xsd:extension base="tdl:Element">
<xsd:choice maxOccurs="unbounded" minOccurs="0">
<xsd:element name="gateInstance" type="tdl:GateInstance"/>
<xsd:element name="variable" type="tdl:Variable"/>
</xsd:choice> ETSI ES 203 119-4 V1.2.1 (2016-09)
<xsd:attribute name="componentType" type="xsd:anyURI">

<xsd:attribute name="role" type="tdl:ComponentInstanceRole"> ETSI STANDARD
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
35
ETSI ES 203 119-1 V1.3.1 (2016-09)
ETSI ES 203 119-3 V1.2.1 (2016-09)

ETSI STANDARD

ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI STANDARD
ETSI STANDARD

ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

<packagedElement xsi:type="tdl:ComponentType" xmi:id="_qKt233asEeWrfP0MdfQNpg" name="ct">

<gateInstance xmi:id="_qKt24HasEeWrfP0MdfQNpg" name="g" type="_qKt23nasEeWrfP0MdfQNpg"/>
</packagedElement>
36
What is TDL? Part 4: TO
ETSI ES 203 119-1 V1.3.1 (2016-09)
• Based on TPLan
ETSI ES 203 119-4 V1.2.1 (2016-09)
ETSI STANDARD

• refine test objectives

!
• formalise specification ETSI STANDARD

ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD
• integrate and unify test   Methods for Testing and Specification (MTS); Methods for Testing and Specification (MTS);

description and test purpose  

specification
ETSI ES 203 119-3 V1.2.1 (2016-09)
ETSI STANDARD

37
ETSI ES 203 119-1 V1.3.1 (2016-09)
Base Standard Specification ETSI ES 203 119-4 V1.2.1 (2016-09)

ETSI STANDARD

Identification of Requirements
!
ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI STANDARD
Creation of ICS/IFS
ETSI STANDARD
Methods for Testing and Specification (MTS); Methods for Testing and Specification (MTS);

Definition of TSS
ETSI ES 203 119-3 V1.2.1 (2016-09)
Specification of Test Purposes

ETSI STANDARD

Specification of Test Descriptions
Specification of Test Cases
Validation
38
ETSI ES 203 119-1 V1.3.1 (2016-09)

ETSI STANDARD

!
ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI STANDARD
Creation of ICS/IFS
ETSI STANDARD

Definition of TSS
ETSI ES 203 119-3 V1.2.1 (2016-09)

ETSI STANDARD

Validation
39
ETSI ES 203 119-1 V1.3.1 (2016-09)

ETSI STANDARD

!
ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI STANDARD
Creation of ICS/IFS
ETSI STANDARD

Definition of TSS
ETSI ES 203 119-3 V1.2.1 (2016-09)

ETSI STANDARD

Validation
40
ETSI ES 203 119-1 V1.3.1 (2016-09)
Test Purpose { ETSI ES 203 119-4 V1.2.1 (2016-09)

TP Id "TP/CAM/INA/DOP/BV/02"
ETSI STANDARD

Test objective "Checks that CAM message includes

DoorOpen information 30s after closed"

Reference "TS 102 637-2 [1], clauses 7.1 and 7.2" !
PICS Selection PICS_PUBTRANSVEH ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI STANDARD
Initial conditions
with { ETSI STANDARD
the IUT entity having reached an initial_state Methods for Testing and Specification (MTS); Methods for Testing and Specification (MTS);
and Part 4: Structured Test Objective Specification (Extension)
the IUT entity having sent a valid CAM message

containing DoorOpen TaggedValue;
} ETSI ES 203 119-3 V1.2.1 (2016-09)
Expected behaviour ETSI STANDARD
ensure that { Methods for Testing and Specification(MTS);

when {
the door entity is closed
}
then {
the IUT entity sends a new CAM message
containing DoorOpen TaggedValue;
}
}
}
41
What is TDL?
ETSI ES 203 119-1 V1.3.1 (2016-09) ETSI ES 203 119-2 V1.2.1 (2016-09)
ETSI STANDARD ETSI STANDARD
Part 1: Abstract Syntax and Associated Semantics Part 2: Graphical Syntax
ETSI ES 203 119-3 V1.2.1 (2016-09) ETSI ES 203 119-4 V1.2.1 (2016-09)
Part 3: Exchange Format Part 4: Structured Test Objective Specification (Extension)
42
What is TDL?
ETSI ES 203 119-1 V1.3.1 (2016-09) ETSI ES 203 119-2 V1.2.1 (2016-09)
Part 1: Abstract Syntax and Associated Semantics Part 2: Graphical Syntax
ETSI ES 203 119-3 V1.2.1 (2016-09) ETSI ES 203 119-4 V1.2.1 (2016-09)
Part 3: Exchange Format Part 4: Structured Test Objective Specification (Extension)
43
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )
ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2

ETSI 016-09)
ETSI STAND
ARD
ETSI STA
NDA RD
ETSI STANDARD
Methods fo
ETSI STANDARD r Testi
The o st De ng and Specification
M
Part 4: Stru ethTe ds for sc
Tesription Lang (MTS);
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
esjec tive dSpSpecific(TDL );
The Test Description crip ec(MT
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Testing Syntax Spe L an xte
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
t 2: Gra Associated uageSemantics
(TDL);
The Tes t Des crip S yn tax
han ge For ma t
Part 3: Exc
44
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )
ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2

ETSI 016-09)
ETSI STAND
ARD
ETSI STA
NDA RD
ETSI STANDARD
Methods fo
M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
(TDL);
han ge For ma t
Part 3: Exc
45
Why TDL?
• Model-based Testing
• modelling features to describe and generate abstract tests
• Test automation ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 )
19-2) (2016-09)
ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2
ETSI
• support for common testing patterns

016-09
ETSI STAND
ARD
ETSI STA
• clear semantics for generating concrete tests

NDA RD
ETSI STANDARD
Methods fo
M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
(TDL);
Tes t Des crip S yn ta
• Agile Development
The ge For ma t x
Part 3: Exc han
• test-driven and behaviour-driven development

• scenario-based testing from user stories
!
• multiple representation formats for different stakeholders
46
Why TDL?
• For users
• separate test specification from test implementation
• amenable to tool-supported verification ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )
• adjustable to stakeholders
ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2
ETSI 016-09
ETSI STAND
ARD

ETSI STA
NDA RD
ETSI STANDARD
Methods fo
M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
forAbstract
ds 1: (TDgL);

Metho
Part tion Lanandguaphge
ical (TDL);
han ge For ma t
Part 3: Exc
• universal standardised exchange format


• focus on core expertise, add value through interoperability
47
Why TDL?
• Transparent change management
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )
ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2

ETSI 016-09
ETSI STAND
ARD
ETSI STA
NDA RD
ETSI STANDARD
Methods fo
M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
(TDL);
han ge For ma t
Part 3: Exc
48 TDL Project at http://forge.etsi.org/mantis/view_all_bug_page.php

Why TDL?
• Proof by implementation
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )
ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2

ETSI 016-09
ETSI STAND
ARD
ETSI STA
NDA RD
ETSI STANDARD
Methods fo
M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
(TDL);
han ge For ma t
Part 3: Exc
49 TDL Website at tdl.etsi.org

Why TDL?
• Why not UTP?

• requires knowledge and understanding of UML
• loose semantics inherited from UML ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )
• tool-specific implementations
ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2
ETSI 016-09
ETSI STAND
ARD
• poor transferability as a consequence

ETSI STA
NDA RD
ETSI STANDARD
Methods fo
M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
forAbstract
ds 1: (TDgL);
• additional profiles for timing aspects

Metho
Part tion Lanandguaphge
ical (TDL);
han ge For ma t
Part 3: Exc
50
A more comprehensive example…
Structured Data Instance Structured Data Type
Request:Message Message
sessionId:= sessionId:Integer
content:=Greeting001 content:String
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )
ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2

ETSI 016-09
Node
ETSI STAND
ARD
Data Variable
ETSI STA
ETSI STANDARD
NDA RD
Data Type: Message name:String ETSI STANDARD

Methods fo
M
Part 4: Stru ethTe
ctu
r Testi
ds for sc
socket:Data Methods Tre

edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
(TDL);
han ge For ma t
Part 3: Exc
Test Configuration
ClientAndServer
!
TESTER SUT
Server:Node socket socket Client:Node
51
TESTER SUT
Server:Node Client:Node
socket socket
Request (sessionId := 1)
• Atomic
alternative
Accept (sessionId := 1)
PASS
• Combined ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )
Accept (sessionId := ?) ETSI ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2

016-09
ETSI STAND
ARD
ETSI STA
FAIL
NDA RD
ETSI STANDARD
Methods fo
M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
(TDL);
ge For ma t
• Exceptional
Part 3: Exc han
interrupt Tick
Tock
!
default Reject
INCONCLUSIVE
52
TESTER SUT
socket socket
alternative
PASS
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )

016-09
ETSI STAND
ARD
ETSI STA
FAIL
NDA RD
ETSI STANDARD
Methods fo
M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
(TDL);
han ge For ma t
Part 3: Exc
interrupt Tick
Tock
!
default Reject
INCONCLUSIVE
53
TESTER SUT
socket socket
alternative
PASS
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )

016-09
DEMO FAIL
ETSI STAND
ETSI STA
ETSI STANDARD
ARD
NDA
Methods fo
RD

M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
(TDL);
han ge For ma t
Part 3: Exc
interrupt Tick
Tock
!
default Reject
INCONCLUSIVE
54
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 1V1.3.1
119-1 19-2) (2016-09) )
ES 20 3 119-3 V1.2.1 (2016-09 V1.2.1 (2

ETSI 016-09)
ETSI STAND
ARD
ETSI STA
NDA RD
ETSI STANDARD
Methods fo
M
ctu
Methods Tre
edTTe
hfor Testing tiand
ng an uage
es st
t DOb
Language
tio
cificat
n ion S);
ificatiaton
ion(E(M
(TDL);
Pand
ar
Tns
S);ion)
Metho
Part forAbstract
ds 1:
tion Lanandguaphge
ical(TDgL);
(TDL);
han ge For ma t
Part 3: Exc
55
Where does TDL fit in?
Front-end tool Back-end tool Artefact (output) (Partially) Covered in reference implementation
TDL Model
Textual Editor   UML-based Graph. Report TDL Test Generator
Analyser
(incl. ES 203119-4) Editor
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
9-9)2
)
ETSI ES 203 119-3 V1.2.1 (2016-0 V1.2.1 (2016-09)
ETSI STANDAR
D
ETSI STA
NDARD
ETSI STANDARD
Methods for
ETSI STANDARD Test
The Test Descing and Specification
Me
Part 4: Stru tho ds for Tesription Lang (MTS);
ctur
Methods for
Thed Testing ting and uage (TDL
e Test
Tes Objeand Specification
Specifica
(MTS);
);
t De scrctive
Language
iption ;tion
ifica(TDL);
TestingPa
forAbstract and Specif
rt 2: Lan(MTS)
ication tion
guageSemantics (MT
(Ext ensi
S); on)
ds 1:
Part Syntax Gra
and Associated
Metho ph ica(TDL);
age (TDL);
TDL Exchange Format (ES 203119-3)

Langu l
The Test Descriptionnge Format Syntax
Part 3: Excha
 
Graph. Viewer & Test Code C-code,
Graphical Editor  Test Plan

Doc. Gen. Generator TTCN-3
(ES 203119-2)
56
Keyword-Driven Testing
MBT ETSI ES 20
Representation
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
9-9)2
)
Generation
ETSI ES 203 119-3 V1.2.1 (2016-0 V1.2.1 (2016-09)
ETSI STANDAR
D
ETSI STA
NDARD
ETSI STANDARD
Methods for
ETSI STANDARD
Visualisation
Test
Me
ctur
Methods for
e Test
Specifica
(MTS);
);
t De scrctive
Language
iption ;tion
ifica(TDL);
TestingPa
rt 2: Lan(MTS)
ication tion
guageSemantics (MT
(Ext ensi
S); on)
ds 1:
Part Syntax Gra
and Associated
Metho Langu ph ica(TDL);
age l
(TDL);
Part 3: Excha
Standards !
Documentation ITS
57
ETSI ES 20
HTML D
OC
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
9-9)2
)
ETSI ES 203 119-3 V1.2.1 (2016-0 V1.2.1 (2016-09)
ETSI STANDAR
D
ETSI STA
NDARD
ETSI STANDARD
Methods for
PDF
ETSI STANDARD Test
Me
ctur
Methods for
e Test
Specifica
(MTS);
);
t De scrctive
Language
iption ;tion
ifica(TDL);
TestingPa
rt 2: Lan(MTS)
ication tion
guageSemantics (MT
(Ext ensi
S); on)
ds 1:
Part Syntax Gra
and Associated
age l
(TDL);
Part 3: Excha
Documentation
58
ETSI ES 20
HTML D
OC
ETSI ES 3 119-4 V1.2.1 (2016-09
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
9-9)2
)
ETSI ES 203 119-3 V1.2.1 (2016-0 V1.2.1 (2016-09)
ETSI STANDAR
D
ETSI STA
NDARD
ETSI STANDARD
Methods for
PDF
ETSI STANDARD Test
Me
ctur
Methods for
e Test
Specifica
(MTS);
);
t De scrctive
Language
iption ;tion
ifica(TDL);
TestingPa
rt 2: Lan(MTS)
ication tion
guageSemantics (MT
(Ext ensi
S); on)
ds 1:
Part Syntax Gra
and Associated
age l
(TDL);
Part 3: Excha
59
HTMLDOC
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 9-2) (2016-09)
V1.3.1
3 V1.2.1 (2016-09 V1.2.1 (201
ETSI ES 203 119- 6-09)
ETSI STAND
ARD
ETSI STAN
DARD
ETSI STANDARD
Methods for
PDF
The Test Descr g and Specification
Met
Part 4: Struc hod s for Tesiption Langu (MTS);
Methods tured
The
forTes
Testing ting
andand age
Test Objec
criptive
The Test Description Speci
Language
tionation(MT S);
atio
ficatio
(TDL);
n n(Exten
TestingPart Specific
and2: Langua (MTS);
sion)
Part 1:
Methods for
Abstract Syntax Gra
andphic (TDL); geSemantics
Associated
eal (TDL);
ion Languag Syntax
The Test Descript e Format
Part 3: Exchang
• Context
• Conformance and interoperability test descriptions
• Standardised test specifications for various ETSI
technologies
• Typically protocol oriented, used in certification schemes
• End-to-end interoperability of systems involving different
equipment
60
HTMLDOC
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 9-2) (2016-09)
V1.3.1
3 V1.2.1 (2016-09 V1.2.1 (201
ETSI ES 203 119- 6-09)
ETSI STAND
ARD
ETSI STAN
DARD
ETSI STANDARD
Methods for
PDF
Met
Methods tured
The
forTes
Testing ting
andand age
Test Objec
criptive
Language
tionation(MT S);
atio
ficatio
(TDL);
n n(Exten
and2: Langua (MTS);
sion)
Part 1:
Methods for
Abstract Syntax Gra
Associated
eal (TDL);
ion Languag Syntax
Part 3: Exchang
• Stakeholders
• High-level discussions at large meetings (80-100 participants)
• ETSI Technical Committees, 3GPP, other standards organisations,
CTI Plugtests team and participants, industrial fora and equipment
vendors
• all need to be familiar with and fluent in the syntax being used
• different notions of “good” test
• Better comprehension among developers with little or no
testing expertise
• bridge the gap between management, core specifications experts,
testing experts
61
HTMLDOC
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 9-2) (2016-09)
V1.3.1
3 V1.2.1 (2016-09 V1.2.1 (201
ETSI ES 203 119- 6-09)
ETSI STAND
ARD
ETSI STAN
DARD
ETSI STANDARD
Methods for
PDF
Met
Methods tured
The
forTes
Testing ting
andand age
Test Objec
criptive
Language
tionation(MT S);
atio
ficatio
(TDL);
n n(Exten
and2: Langua (MTS);
sion)
Part 1:
Methods for
Abstract Syntax Gra
Associated
eal (TDL);
ion Languag Syntax
Part 3: Exchang
• Challenges
• Informal (Word, Excel) or semi-formal (TPLan) approaches
• considered inadequate, no test descriptions as a consequence
• no single consistent approach, varying level of quality, detail,
difficult maintenance
• certification requires completeness and accuracy, test descriptions
are the design stage before developing TTCN-3 test cases
• Acceptance for more rigorous approaches among Technical
Committees
• applicable to a wide range of technologies (protocols, services,
applications)
62
HTMLDOC
ETSI ES 203
TTCN-3
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 9-2) (2016-09)
V1.3.1
3 V1.2.1 (2016-09 V1.2.1 (201
ETSI ES 203 119- 6-09)
ETSI STAND
ARD
ETSI STAN
DARD
ETSI STANDARD
Methods for
PDF
Met
Methods tured
The
forTes
Testing ting
andand age
Test Objec
criptive
Language
tionation(MT S);
atio
ficatio
(TDL);
n n(Exten
and2: Langua (MTS);
sion)
Part 1:for
Methods Abstract Syntax Gra
andphic
ion Languag (TDL); geSemantics
Associated
eal (TDL);
The Test Descript Syntax
e Format
Part 3: Exchang
• TDL
• Standardised approach improves consistency
• Tools offer faster development, higher quality, easier
maintenance
• Direct link to TTCN-3
• Initial run within ITS, expand to other Technical
Committees
63
HTMLDOC
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 9-2) (2016-09)
V1.3.1
3 V1.2.1 (2016-09 V1.2.1 (201
ETSI ES 203 119- 6-09)
ETSI STAND
ARD
ETSI STAN
DARD
ETSI STANDARD
Methods for
PDF
Met
Methods tured
The
forTes
Testing ting
andand age
Test Objec
criptive
Language
tionation(MT S);
atio
ficatio
(TDL);
n n(Exten
and2: Langua (MTS);
sion)
Part 1:
Methods for
Abstract Syntax Gra
Associated
eal (TDL);
ion Languag Syntax
Part 3: Exchang
From 3GPP TS 36.523-1 V10.2.0 (2012-09):

7.2.2.3 UM RLC / Reassembly / 5-bit SN / LI value > PDU size
7.2.2.3.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives a 5 bit SN configured RLC PDU with Length Indicator value larger than RLC PDU
size }
then { UE discards the RLC PDU }
}
7.2.2.3.3.2 Test procedure sequence

7.2.2.3.2 Conformance requirements
Table 7.2.2.3.3.2-1: Main behaviour
See TS 36.322 clauses 6.2.2.5 and 5.5.1
St Procedure Message Sequence TP Verdict
References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.5.1 and
6.2.2.5. U-S Message
- EXCEPTION: the behaviour described in table - - - -
[TS 36.322, clause 5.5.1]
7.2.2.3.3.2-2 runs in parallel with steps 1 to 5
below.
When
1 an RLC
The SS entity receives
transmits UMD an RLC containing
PDU#1 PDU that contains
first reserved
<-- UMD or invalid
PDU#1 values,
(SN=0) the RLC entity shall:
- -
segment of RLC SDU#1.
2- discard
The SSthe received
transmits PDU.
UMD PDU#2 containing last <-- UMD PDU#2 (SN=1) - -
segment of RLC SDU#1 and first segment of
[TS 36.322,
RLC clause
SDU#2.6.2.2.5]
3 The SS transmits UMD PDU#3 containing last <-- UMD PDU#3 (SN=2) - -
Length:segment
11 bits. of RLC SDU#2, first segment of RLC
SDU#3 and with Length Indicator that points
The LI field
beyondindicates
the endthe length
of the UMDin PDU#3.
bytes of the corresponding Data field element present in the RLC data PDU
delivered/received
4 by an UMD
The SS transmits UM orPDU#4
an AMcontaining
RLC entity.
lastThe first
<-- LI UMD
present in the(SN=3)
PDU#4 RLC data PDU header corresponds
- - to the
first Data field element present in the Data field of the RLC data PDU, the second LI present in the RLC data PDU
5 corresponds
header The SS transmits
to theUMD PDU#5
second Datacontaining RLCpresent
field element <--in the
UMD PDU#5
Data field (SN=4)
of the RLC data PDU, and- so on. The
-
64 SDU#4.
value 0 is reserved.
From 3GPP TS 36.523-1 V10.2.0 (2012-09):
7.2.2.3 UM RLC / Reassembly / 5-bit SN / LI value > PDU size
7.2.2.3.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state }
ensure that {
when { UE receives a 5 bit SN configured RLC PDU with Length Indicator value larger than RLC PDU
size }
then { UE discards the RLC PDU }
}
7.2.2.3.3.2 Test procedure sequence

7.2.2.3.2 Conformance requirements
Table 7.2.2.3.3.2-1: Main behaviour
See TS 36.322 clauses 6.2.2.5 and 5.5.1
References: The conformance requirements covered in the present TC are specified in: TS 36.322, clause 5.5.1 and
6.2.2.5. U-S Message
- EXCEPTION: the behaviour described in table - - - -
[TS 36.322, clause 5.5.1]
7.2.2.3.3.2-2 runs in parallel with steps 1 to 5
below.
When
1 an RLC
The SS entity receives
transmits UMD an RLC containing
PDU#1 PDU that contains
first reserved
<-- UMD or invalid
PDU#1 values,
(SN=0) the RLC entity shall:
- -
2- discard
The SSthe received
transmits PDU.
UMD PDU#2 containing last <-- UMD PDU#2 (SN=1) - -
segment of RLC SDU#1 and first segment of
[TS 36.322,
RLC clause
SDU#2.6.2.2.5]
3 The SS transmits UMD PDU#3 containing last <-- UMD PDU#3 (SN=2) - -
Length:segment
11 bits. of RLC SDU#2, first segment of RLC
SDU#3 and with Length Indicator that points
The LI field
beyondindicates
the endthe length
of the UMDin PDU#3.
bytes of the corresponding Data field element present in the RLC data PDU
delivered/received
4 by an UMD
The SS transmits UM orPDU#4
an AMcontaining
RLC entity.
lastThe first
<-- LI UMD
present in the(SN=3)
PDU#4 RLC data PDU header corresponds
- - to the
segment
first Data of RLC present
field element SDU#3.in the Data field of the RLC data PDU, the second LI present in the RLC data PDU
header corresponds to theUMD
5 The SS transmits PDU#5
second Datacontaining RLCpresent
field element <--in the
UMD PDU#5
Data field (SN=4)
of the RLC data PDU, and- so on. The
-
value 0 SDU#4.
is reserved.
7.2.2.3.3 Test description

Table 7.2.2.3.3.2-2: Parallel behaviour
7.2.2.3.3.1 Pre-test conditions
System Simulator: U-S Message
1- The 1.
Cell UE transmits RLC SDU#1. --> (RLC SDU#1) - -
2 Check: Does the UE transmit RLC SDU#2? --> (RLC SDU#2) 1 F
UE:
3 Check: Does the UE transmit RLC SDU#3? --> (RLC SDU#3) 1 F
None.
4 The UE transmits RLC SDU#4. --> (RLC SDU#4) - -
65
Preamble:
From 3GPP TS 36.523-1 V10.2.0 (2012-09):
66
114 ETSI TS 186 011-2 V3.1.1 (2011-06)
From ETSI TS 186 011-2 V3.1.1 (2011-06): 114 ETSI TS 186 011-2 V3.1.1 (2011-06)
4.5.1 General Capabilities

4.5.1.1 SIP messages longer than 1 500 bytes
4.5.1.1 SIP messages longer than 1 500 bytes
Interoperability Test Description
Identifier: Interoperability Test Description
TD_IMS_MESS_0001
Identifier:
Summary: TD_IMS_MESS_0001
IMS network shall support SIP messages greater than 1 500 bytes
Summary:
Configuration: IMS network shall support SIP messages greater than 1 500 bytes
CF_INT_CALL
Configuration:
SUT CF_INT_CALL
IMS_B
SUT
References IMS_B
Test Purpose Specification Reference
References Test Purpose
TP_IMS_4002_1 Specification
TS 124 229 [1],Reference
clause 4.2A ¶1
Use Case ref.: TP_IMS_4002_1
UC_05_I TS 124 229 [1], clause 4.2A ¶1
Use Case ref.: UC_05_I
Pre-test • HSS of IMS_A and of IMS B is configured according to table 1
Pre-test
conditions: •• HSS
UE_AofandIMS_A
UE_B and of IMS
have B is configured
IP bearers according
established to theirtorespective
table 1 IMS networks as
conditions: • UE_A
per and UE_B
clause 4.2.1 have IP bearers established to their respective IMS networks as
• per
UE_Aclause 4.2.1 configured to use TCP for transport
and IMS_A
•• UE_A
UE_A is registeredconfigured
and IMS_A in IMS_A usingto useany
TCP for identity
user transport
•• UE_A
UE_B isis registered
registered in IMS_A
user usingusing
of IMS_B any user
any identity
user identity
•• UE_B is registered user of IMS_B using
MESSAGE request and response has to be supported any user identityat II-NNI (TS 129 165 [16]
• MESSAGE
see request
tables 6.1 and response has to be supported at II-NNI (TS 129 165 [16]
and 6.3)
see tables 6.1 and 6.3)
Test Sequence: Step
Test Sequence: Step
1 User A sends message to User B with at least 1 500 characters
1
2 User Athat
Verify sends
usermessage
B receives to User B with
message at least
from user 1A500 characters
2 Verify that user B receives message from user A
Conformance Check
Conformance
Criteria: Check
1 TP_IMS_4002_01 in CFW step 4 (MESSAGE)
Criteria: 1 TP_IMS_4002_01
ensure that { in CFW step 4 (MESSAGE)
ensure that {
when { UE_A sends a MESSAGE to UE_B
when { containing
UE_A sends a MESSAGE togreater
a Message_Body UE_B than 1 300 bytes }
containing a Message_Body
then { IMS_B receives the MESSAGE greater than 1 300 bytes }
then { IMS_B receives
containing the MESSAGEgreater than 1 300 bytes }
the Message_Body
} containing the Message_Body greater than 1 300 bytes }
}
115 ETSI TS 186 011-2 V3.1.1 (2011-06)
115 ETSI TS 186 011-2 V3.1.1 (2011-06)
Step Direction Message Comment

Step U U I Direction
I I I U U Message Comment
U
s U
E I
M BI BI I
M U
E U
s
s
e E
A M
S B
C B
C M
S E
B s
e
er A S
A C
F C
F S
B B er
Ar A F
A F
B B Br
1 A A B B User A sends an instant message to user B
1 User A sends an instant message to user B
67 2
2
MESSAGE
MESSAGE
UE_A sends MESSAGE to IMS_A
UE_A sends MESSAGE to IMS_A
• MESSAGE request and response has to be supported at II-NNI (TS 129 165 [16]
From ETSI TS 186 011-2 V3.1.1 (2011-06):

Test Sequence: Step
114 ETSI TS 186 011-2 V3.1.1 (2011-06)
1 User A sends message to User B with at least 1 500 characters

Conformance Check
4.5.1.1
Criteria: SIP messages
1 longer than 1 500
TP_IMS_4002_01 bytes
in CFW step 4 (MESSAGE)
ensure that {
Interoperability
when { UE_A sends a Test Description
MESSAGE to UE_B
Identifier: TD_IMS_MESS_0001 containing a Message_Body greater than 1 300 bytes }
Summary: IMS networkthen
shall{ support
IMS_B receives the MESSAGE
SIP messages greater than 1 500 bytes
Configuration: CF_INT_CALL containing the Message_Body greater than 1 300 bytes }
SUT IMS_B }
References Test Purpose Specification Reference
TP_IMS_4002_1 115 TS 124ETSI
229 TS
[1],186 011-24.2A
clause V3.1.1
¶1(2011-06)
Use Case ref.: UC_05_I
Pre-test
U U I •I HSSI of IMS_A
I U of U
and IMS B is configured according to table 1
s E
conditions: M •B B M E s
UE_A and UE_B have IP bearers established to their respective IMS networks as
e A S C C S
per clause 4.2.1B e
r A F F B r
A •A UE_A B and IMS_A configured
B to use TCP for transport
1 • UE_A is registered in IMS_A using any user identity
User A sends an instant message to user B
• UE_B is registered user of IMS_B using any user identity
2 • MESSAGE request and response
MESSAGEhas toUE_A
be supported at II-NNI
sends MESSAGE to (TS 129 165 [16]
IMS_A
3 MESSAGE IMS_A sends MESSAGE to IBCF_A
Test Sequence: Step
4 1 User A sends message MESSAGE
to User BIBCF_A
with at sends
least 1MESSAGE to IBCF_B
500 characters
5 MESSAGE IBCF_B sends MESSAGE to IMS_B with via
Conformance Check header indicating TCP
6 Criteria: 1 TP_IMS_4002_01 inMESSAGE
CFW step 4 IMS_B sends MESSAGE to UE_B
(MESSAGE)
ensure that {
7 when { UE_A sends a MESSAGE User B is informed about the instant message
to UE_B
containing a Message_Body greater than 1 300 bytes }
8 200 OK
then { IMS_B receives UE_B sends 200 OK to IMS_B
the MESSAGE
containing the Message_Body greater than 1 300 bytes }
9 } 200 OK IMS_B sends 200 OK to IBCF_B
10 200 OK
115 IBCF_B ETSI
sendsTS
200 OK011-2
186 to IBCF_A
V3.1.1 (2011-06)
11 200 OK IBCF_A sends 200 OK to IMS_A

U U I I I I U U
12 s E M B B M E s 200 OK IMS_A sends 200 OK to UE_A
e A S C C S B e
13 r A F F B r Optional: User A is presented a delivery report
A A B B
1 User A sends an instant message to user B
ETSI
68 2 MESSAGE UE_A sends MESSAGE to IMS_A
From ETSI TS 186 011-2 V3.1.1 (2011-06):
69
HTMLDOC
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 9-2) (2016-09)
V1.3.1
3 V1.2.1 (2016-09 V1.2.1 (201
ETSI ES 203 119- 6-09)
ETSI STAND
ARD
ETSI STAN
DARD
ETSI STANDARD
Methods for
PDF
Met
Methods tured
The
forTes
Testing ting
andand age
Test Objec
criptive
Language
tionation(MT S);
atio
ficatio
(TDL);
n n(Exten
and2: Langua (MTS);
sion)
Part 1:
Methods for
Abstract Syntax Gra
Associated
eal (TDL);
ion Languag Syntax
Part 3: Exchang
From ETSI TS 102 868-2 V1.1.1 (2011-03):

16 ETSI TS 102 868-2 V1.1.1 (2011-03)
TP Id TP/CAM/INA/DOP/BV/02
Test objective Checks that CAM message includes DoorOpen information 30s after closed
Reference TS 102 637-2 [1], clauses 7.1 and 7.2
PICS Selection PICS_PUBTRANSVEH
Initial conditions
with {
the IUT being in the "initial state" and
the IUT having sent a valid CAM message
containing DoorOpen TaggedValue
}
Expected behaviour
ensure that {
when {
the door is closed
}
then {
the IUT sends CAM messages
containing DoorOpen TaggedValue during the 30s following the door closing event
}
}
TP Id TP/CAM/INA/DOP/BV/03
Test objective Checks that CAM message includes DoorOpen informationwhen supported
Reference TS 102 637-2 [1], clauses 7.1 and 7.2
PICS Selection PICS_PUBTRANSVEH OR PICS_DOOROPEN
Initial conditions
with {
the IUT being in the "initial state"
}
Expected behaviour
70 ensure that {
when {
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 9-2) (2016-09)
V1.3.1
3 V1.2.1 (2016-09 V1.2.1 (201
ETSI ES 203 119- 6-09)
ETSI STAND
ARD
ETSI STAN
DARD
ETSI STANDARD
Methods for
Met
Methods tured
The
forTes
Testing ting
andand age
Test Objec
criptive
Language
tionation(MT S);
atio
ficatio
(TDL);
n n(Exten
and2: Langua (MTS);
sion)
Part 1:
Methods for
Abstract Syntax Gra
Associated
eal (TDL);
ion Languag Syntax
Part 3: Exchang
71
ETSI ES 203
ET ES 119-4 V1.2.1 (2016-09)
ETSI ESSI203 203 11
119-1 V1.3.1 (2016-09)
9-2) V1.2.1
TTCN-3
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
ETSI STANDARD
Methods for
ETSI STANDARD Testi
The Test Descng and Specification
Met
Part 4: Struc hod s for Tesription Lang (MTS);
Methodstured
for
The Testing ting
andand uage
Test
Tes Objec
t Des Specific(TDL);
criptive
The Test Description tionSpec
Language TS);
(TDL);
ificat
ation(M atio (MT
TestingPar
forAbstract and Specific
t 2: Langua ion n(Exte nsion
S); )
Parts 1:
Method Syntax Gra
and (TDL); geSemantics
Associated
ge
phi (TDL);
tion Langua cal Syntax
The Test Descrip ge Format
Part 3: Exchan
• Context
• TDL in MBT: Keyword driven UI testing
• Create behavioural model of the SUT using symbolic action
descriptions
• define keywords once
• map abstract keyword definitions to keyword implementations in
execution language
• Generate abstract test sequences by means of MBT
• Convert abstract test sequences to a test execution
language
72
ETSI ES 203
ET ES 119-4 V1.2.1 (2016-09)
ETSI ESSI203 203 11
119-1 V1.3.1 (2016-09)
9-2) V1.2.1
TTCN-3
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
ETSI STANDARD
Methods for
ETSI STANDARD Testi
Met
Methodstured
for
The Testing ting
andand uage
Test
Tes Objec
criptive
Language TS);
(TDL);
ificat
ation(M atio (MT
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
ge
phi (TDL);
Part 3: Exchan
• Challenges
• Generated test sequences
• proprietary format - not accessible, tool-specific integrations to
requirements management, test planning
• straight to executable code - loss of meta-data, difficult
parameterisation
• Mapping between abstract (symbolic) and real test system
interface
• implicit - error-prone
• implemented in test execution language - additional overhead,
language limitations
73
ETSI ES 203
ET ES 119-4 V1.2.1 (2016-09)
ETSI ESSI203 203 11
119-1 V1.3.1 (2016-09)
9-2) V1.2.1
TTCN-3
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
ETSI STANDARD
Methods for
ETSI STANDARD Testi
Met
Methodstured
for
The Testing ting
andand uage
Test
Tes Objec
criptive
Language TS);
(TDL);
ificat
ation(M atio (MT
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
ge
phi (TDL);
Part 3: Exchan
• TDL
• Interoperability with requirements management by
explicit test objectives
• Parameterisation of test descriptions and symbolic data
representations
• Explicit data mapping to underlying data system of
execution language
• Advantages over alternatives
• Less ambiguity, testing specific (e.g. break, stop, default
concepts)
74
ETSI ES 203
ET ES 119-4 V1.2.1 (2016-09)
ETSI ESSI203 203 11
119-1 V1.3.1 (2016-09)
9-2) V1.2.1
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
ETSI STANDARD
Methods for
ETSI STANDARD Testi
Met
Methodstured
for
The Testing ting
andand uage
Test
Tes Objec
criptive
Language TS);
(TDL);
ificat
ation(M atio (MT
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
ge
phi (TDL);
Part 3: Exchan
Representation
Generation
Visualisation
75
HTMLDOC
ETSI ES 203
ET ES 119-4 V1.2.1 (2016-09)
ETSI ESSI203 203 11
119-1
TTCN-3
V1.3.1 (2016-09)
9-2) V1.2.1
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
ETSI STANDARD
PDF
Methods for
ETSI STANDARD Testi
Met
Methodstured
for
The Testing ting
andand uage
Test
Tes Objec
criptive
Language TS);
(TDL);
ificat
ation(M atio (MT
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
ge
phi (TDL);
Part 3: Exchan
• Context
• Test automation tools for performance and load tests
• Challenges
• Textual test specifications with sequence diagram-like
examples (or using a different graphical notation)
• Manual derivation of TTCN-3 code and configuration
settings
• Too wide a gap between input and output!
76
HTMLDOC
ETSI ES 203
ET ES 119-4 V1.2.1 (2016-09)
ETSI ESSI203 203 11
119-1
TTCN-3
V1.3.1 (2016-09)
9-2) V1.2.1
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
ETSI STANDARD
PDF
Methods for
ETSI STANDARD Testi
Met
Methodstured
for
The Testing ting
andand uage
Test
Tes Objec
criptive
Language TS);
(TDL);
ificat
ation(M atio (MT
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
ge
phi (TDL);
Part 3: Exchan
• TDL
• Raises the abstraction level of the test description
• multiple levels of test specification (from system to
implementation), iterative and agile development
• Concentrate on the problems themselves rather than
programming details
• Application
• Visualisation of test case behaviour
• Automatic generation of TTCN-3 code from TDL test
descriptions
77
ETSI ES 203
ET ES 119-4 V1.2.1 (2016-09)
ETSI ESSI203 203 11
119-1 V1.3.1 (2016-09)
9-2) V1.2.1
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
ETSI STANDARD
Methods for
ETSI STANDARD Testi
Met
Methodstured
for
The Testing ting
andand uage
Test
Tes Objec
criptive
Language TS);
(TDL);
ificat
ation(M atio (MT
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
ge
phi (TDL);
Part 3: Exchan
MBT Representation
Generation
Standards
78
ETSI ES 20
ETSI ES 3 119-4 V1.2.1 (2016-09
203 11
TTCN-3
ETSI ES 203 119-1 V1.3.1
9-9)2(2016-09)
)
-3 V1.2.1 (2016-0 V1.2.1 (20

ETSI ES 203 119 16-09)
ETSI STANDAR
D
ETSI STA
NDARD
ETSI STANDARD
Methods for
ETSI STANDARD Test
Me
ctur
Methods Thed
for Testing ting and uage (TDL
e Test
Specifica (MTS);
);
t De scrctive
iption Spec ;tion
ifica(TDL);
TestingPa
rt 2: Lan(MTS)
Language
ication tion
guage (Ext (MT
ensi
S); on)
ds 1: Gra
Part
Metho
Descr
Syntax
iption Languandph ica(TDL);
Associated
age l Syntax
(TDL);
Semantics
The Test Format
Part 3: Exchange
• User Requirements Notation (URN)

• Elicitation, analysis, specification, and validation of
requirements
• Complementary views - goals (GRL) and scenarios (UCM)
• ITU-T Recommendation Z.151 (10/12)
79
TTCN- Clas
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
9-2) V1.2.1
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
sif
ETSI STAND
ARD
ETSI STA
NDARD
3 ied
ETSI STANDARD
Methods for
ETSI STANDARD Testi
Met
Methodstured
Thefor Testing ting
andand uage
Test
Tes Objec
The Test Descriptioncriptive Spec
Language
tion TS);
ificat
ation(M atio (MT
(TDL);
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
geal
phic (TDL);
tion Langua Syntax
Part 3: Exchange
• Context
• Test systems for cockpit systems and avionics solutions
• Alternative means for
• standards-based and model-based test generation and test
automation
• replace proprietary solutions
• Transformation from high-level requirements and scenarios
in UCM to TDL
• Transformation from TDL to TTCN-3
80
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
TTCN-
9-2) V1.2.1
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
3
ETSI STANDARD
Methods for
ETSI STANDARD Testi
Met
Methodstured
Thefor Testing ting
andand uage
Test
Tes Objec
Language
tion TS);
ificat
ation(M atio (MT
(TDL);
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
geal
phic (TDL);
tion Langua Syntax
Part 3: Exchange
• Goals
• URN/UCM suitable starting point for modelling
requirements?
• TDL appropriate intermediate representation or even
starting point?
• TTCN-3 viable technology in the avionics industry?
• Stakeholders
• Research, industry, agencies
• Test engineers, test developers, test managers, analysts
and modellers
81
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
TTCN-
9-2) V1.2.1
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
3
ETSI STANDARD
Methods for
ETSI STANDARD Testi
Met
Methodstured
Thefor Testing ting
andand uage
Test
Tes Objec
Language
tion TS);
ificat
ation(M atio (MT
(TDL);
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
geal
phic (TDL);
tion Langua Syntax
Part 3: Exchange
• Motivation
• Tree-like structure of tests
• TDL/TTCN-3 reflect this, existing transformations from UCM to
e.g. MSC/UML do not
• UCMs do not include much data information
• appropriate stage to add data for executable test cases (UCM/
TDL/TTCN-3/other)?
• Peculiarities of the domain
• support testing in an environment where an unknown number of
sensors can send alarms (over unreliable channels) and messages
in parallel
82
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
TTCN-
9-2) V1.2.1
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
3
ETSI STANDARD
Methods for
ETSI STANDARD Testi
Met
Methodstured
Thefor Testing ting
andand uage
Test
Tes Objec
Language
tion TS);
ificat
ation(M atio (MT
(TDL);
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
geal
phic (TDL);
tion Langua Syntax
Part 3: Exchange
• TDL
• Close enough to UCM for test generation
• Close enough to TTCN-3 for generating executable test
cases and test configurations
• Prototype
• Part of jUCMNav (v6.0.0), developed at EECS (University of
Ottawa)
• Support for sequence and concurrent events (no
alternatives yet)
http://jucmnav.softwareengineering.ca/ucm/bin/view/ProjetSEG/ExportTdlUserGuide
83
ETSI ES 203
ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
TTCN-
9-2) V1.2.1
3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)
ETSI STAND
ARD
ETSI STA
NDARD
3
ETSI STANDARD
Methods for
ETSI STANDARD Testi
Met
Methodstured
Thefor Testing ting
andand uage
Test
Tes Objec
Language
tion TS);
ificat
ation(M atio (MT
(TDL);
TestingPar
S); )
Parts 1:
Method Syntax Gra
Associated
geal
phic (TDL);
tion Langua Syntax
Part 3: Exchange
http://jucmnav.softwareengineering.ca/ucm/bin/view/ProjetSEG/ExportTdlUserGuide
84
Concluding remarks
• New technology, growing rapidly

• Open-source reference implementation
• lower barrier to entry, accelerate adoption
• commercial tool support not yet available
• Custom tools can be put together in a matter of hours
• basic yet capable
• make early adoption easier
• Advanced solutions still require additional effort
• not immediately necessary to get started with using TDL
85
Summary
What is TDL?
Why TDL?
Final draft ETSI ES 203 119-1 V1.2.0 (2015-04)
• Design, documentation, and • For users

representation of formal test ETSI STANDARD • separate test specification from test implementation
descriptions • amenable to tool-supported verification
The Test Description Language (TDL); ETSI ES 203
Part 1: Abstract Syntax and Associated Semantics ETSI ES 119-4 V1.2.1 (2016-09)
ETSI ES 203 203 11
119-1 V1.3.1 (2016-09)
9-2) V1.2.1
• Scenario-based approach • adjustable to stakeholders

3 V1.2.1 (2016-09
ETSI ES 203 119- (2016-09
)

ETSI STAND
ARD

ETSI STA
NDARD
ETSI STANDARD
Methods for
The Test Desc g and Specification
Met
Part 4: Struc hod s for Tes
ription Lang (MTS);
Methodstured
The
for Testing ting
andand uage
Test
Tes Objec
criptive
Language TS);
atio
ificati
TestingPar
forAbstract and tion
Specific
t 2: Langua (TDL);
ation(M on n(Exte
(MTnsion
S); )
Parts 1: (TDL); geSemantics

Method Syntax Gra
and Associated
geal
phic (TDL);
• STF 454 (2013)

tion Langua
The Test Descrip Syntax
Format
Part 3: Exchange
• STF 476 (2014) • universal standardised exchange format

• STF 492 (2015)
!
MBT Representation
Final draft ETSI ES 203

Rail
ETSI ES 119-4 V1.1.0 (2015-04)
Final draft
Final draft ETSI ES 203 119-1
203 119 V1.2.0 (2015-04)
Generation
ES 203 119-3 V1.1.0 -2 V1.1.0 (2015-0
(2015-04)
Final draft ETSI 4)
ETSI STANDARD
• focus on core expertise, add value through interoperability

ETSI STANDA
RD
ETSI STANDARD
Methods for
ETSI STANDARD Testing and
The Test Descriptio
Method Specificati
Part 4: Structured s for Testingn Language on (MTS);
MethodsTheforTest
Testing
Test andand
Objective Specifi (TDL);
Descrip Specificati
cation
Part 2: Language
tion Langua (TDL);
on (Extension
(MTS);
Part 1: Abstract Syntax Graphi
and Associated ge (TDL); )
cal Syntax Semantics
(MTS);
and Specification
Methods for Testing Language (TDL);
3
Format
Part 3: Exchange
Standards !
X Visualisation
Documentation ITS
46
Where would you consider using TDL?
86 tdl.etsi.org
What would you want to see in TDL?
87 tdl.etsi.org
Testing and Modeling with TDL
Philip Makedonski, Gusztav Adamis, Martti Käärik,
Finn Kristoffersen, Andreas Ulrich, Xavier Zeitoun
tdl.etsi.org
© ETSI 2016. All rights reserved

Testing and Modeling With TDL

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Testing and Modeling With TDL

Uploaded by

Copyright:

Available Formats

TESTING AND MODELING WITH TDL

Philip Makedonski, Gusztav Adamis, Martti Käärik,

• Design, documentation, and • For users

• Scenario-based approach • adjustable to stakeholders

• Standardised at ETSI by TC MTS

• focus on what to test vs how

• For tool vendors

• STF 454 (2013)

• STF 476 (2014) • universal standardised exchange format

• support for customers from different domains !

• reuse of and integration with existing tools

3 Keyword-Driven• focus on core expertise, add value through interoperability

MBT Final draft ETSI ES 203

• Test Description Language

• Design, documentation, and

descriptions Methods for Testing and Specification (MTS);

• STF 492 (2015)

• both industry and standardisation

System Requirements Specification Requirements Level

Model TPLan TDL-TO

Test Generator Test Design Level

Test Code Generator

TTCN-3 (or Other Execution Language) Test Implementation Level

Executable Tests Test Execution Level

• describe interactions with a system

• Reactive, distributed, real-time

• clear semantics Methods for Testing and Specification (MTS);

• interoperability and independence

• Siemens AG, Ericsson Hungary

• CEA, University of Göttingen Methods for Testing and Specification (MTS);

• OU Elvior, Cinderella ApS

ETSI ES 203 119-4 V1.2.1 (2016-09)

Methods for Testing and Specification (MTS);

ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI ES 203 119-3 V1.2.1 (2016-09)

Methods for Testing and Specification(MTS);

Methods for Testing and Specification (MTS);

Methods for Testing and Specification (MTS);

ETSI ES 203 119-2 V1.2.1 (2016-09)

ETSI ES 203 119-3 V1.2.1 (2016-09)

Methods for Testing and Specification(MTS);

Methods for Testing and Specification (MTS);

What is TDL? A 'GateType' represents a type of communication points, called

ETSI ES 203 119-1 V1.3.1 (2016-09)

• PackageableElement Methods for Testing and Specification (MTS);

• dataType: DataType [1..*] {unique}

The 'DataType's that can be exchanged via 'GateInstan

There are no constraints specified. ETSI ES 203 119-3 V1.2.1 (2016-09)

Methods for Testing and Specification(MTS);

'GateInstance' represents an instance of a 'GateType'. It is the

Methods for Testing and Specification (MTS);

! " # $ ETSI ES 203 119-1 V1.3.1 (2016-09)

!"#"$%&'()%& " $ $ ETSI STANDARD

Methods for Testing and Specification (MTS);

ETSI ES 203 119-2 V1.2.1 (2016-09)

No comments. ETSI ES 203 119-3 V1.2.1 (2016-09)

Methods for Testing and Specification(MTS);

Methods for Testing and Specification (MTS);

• TDL main ingredients

The Test Description Language (TDL);

• Time ETSI STANDARD

Methods for Testing and Specification(MTS);

• Considers both ease of use   ETSI ES 203 119-3 V1.2.1 (2016-09)