International Telecommunication Union
An Introduction
to
version 3
Dr. Michael Ebner
University Göttingen, Germany
ebner@cs.uni-goettingen.de
ITU-T Study Group 17, Geneva, 5-14 October 2005
About the speaker
ITU-T o Is researcher in the telematics group of
Prof. Dr. D. Hogrefe at the Institute for
Informatics, University of Göttingen, Germany
o Is active in the research area of test
automation, model-based testing, and
protocol modeling
o Working with TTCN-3 since 2000
• Influenced data types and synchronous
communication of TTCN-3
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
2
An Introduction to
Institute for Informatics,
University of Göttingen
ITU-T
44 Nobel Prize-winner
live(d) and work(ed) here
Other 12
departments
George-August-Universität
Göttingen
Center for Informatics
Founded in 1737 by King
George II (England),
who also founded
Princeton U (1746) and
Columbia U (1754)
Department of
Mathematics
2000~
Institute for Informatics
Theory
Group Prof.
Waack
01/2003~
Database Group
Prof. May
Distributed
Systems Group,
Prof. Switzer
Practical Informatics
Group Prof. Neumair
(GWDG)
12 October 2005
Gauß,
Weber,
Hilbert, …
Softw. Eng. Group
Prof. Grabowski
Telematics Group
Prof. Hogrefe
Service Eng. Group
Prof. Margaria
ITU-T Study Group 17, Geneva, 5-14 October 2005
3
Table of contents
ITU-T
12 October 2005
1. Overall view of TTCN-3
2. TTCN-3 en detail
a. Types and values
b. Behavior specification
3. Implementation of TTCN-3
4. Presentation formats
5. Final remarks
ITU-T Study Group 17, Geneva, 5-14 October 2005
4
Why using a standardised test
language?
1(3)
ITU-T
Developer
Integrator
Testing
throughout the
process
Heterogeneity
increases
Systems
Integrator
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
5
Why using a standardised test
language?
2(3)
ITU-T
Developer
Testing tight
to Development
e.g. JUnit
Integrator
Testing tight
to Services
TTCN-3
Systems
Integrator
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
6
Why using a standardised test
language?
3(3)
ITU-T
o Standardised test language
• improves communication
• among developers
• with the customer
• improves transparency
• one test language for all departments
• No proprietary test languages
• reduces costs
• costs of training
• usage of commercial test equipments (tools,
test suites, etc.)
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
7
What is TTCN-3 ?
ITU-T
o The standardised (black-box) test specification and
test implementation language.
o Developed
• by the European Telecommunications Standards
Institute (ETSI) from 1999 to 2001.
• based on the experiences from previous TTCN
versions.
o Applicable for all kinds of black-box testing for
reactive and distributed systems, e.g.
• Telecom systems (ISDN, ATM);
• Mobile (telecom) systems (GSM, UMTS);
• Internet (has been applied to IPv6);
• CORBA based systems.
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
8
TTCN stands for …???
ITU-T
o Tree and Tabular Combined Notation
• For TTCN-1 and TTCN-2
o Testing and Test Control Notation
• Since TTCN-3
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
9
The TTCN-3 series of standards
1(3)
ITU-T
ASN.1
Types &
Values
TTCN-3
Core
Notation
Tabular
Format
Other Types
& Values 2
Graphical
Format
Other Types
& Values 3
Other Types
& Values n
12 October 2005
TTCN-3
User
Presentation
Format n
ITU-T Study Group 17, Geneva, 5-14 October 2005
10
The TTCN-3 series of standards
2(3)
ITU-T
msc mi_synch1_conc1
mtc
ASN.1
Types &
Values
TTCN-3
Core
Notation
ISAP1
MSAP2
Tabular
Format
Other
IDL Types
& Values 2
:
testcase myTestcase
runs on MTCType system TSIType
Other()Types
{
mydefault
:=
& Values 3 activate (OtherwiseFail);
verdict.set(pass);
XML
:
connect(PTC_ISAP1:CP_ISAP1,mtc:CP_ISAP1);
:
map(PTC_ISAP1:ISAP1, system:TSI_ISAP1);
:
Other Types
PTC_ISAP1.start(func_PTC_ISAP1());
& Values n
PTC_MSAP2.start(func_PTC_MSAP2());
Synchronization();
all component.done;
log(”Correct Termination”);
C/C++
Graphical
Format
TTCN-3
User
Presentation
UML
Format n
Testing
Profile
}
:
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
11
The TTCN-3 series of standards
3(3)
Standard (ES) in 6(SG17
parts/ WP3 / Q14)
ITU-T o European
ITU-T Recommendation
• ES
201 873-1: TTCN-3 Core Language
Z.140
• ES
201 873-2: TTCN-3 Tabular Presentation Format
Z.141
(TFT)
• ES
201 873-3: TTCN-3 Graphical Presentation
Z.142
Format (GFT)
New
edition
3.1.1TTCN-3
of TTCN-3
sinceSemantics
June 2005
Z.143
• ES
201 873-4:
Operational
Z.144
• ES
201 873-5: TTCN-3 Runtime Interface (TRI)
Z.145
• ES
201 873-6: TTCN-3 Control Interface (TCI)
•
•
•
•
12 October 2005
ES
201 873-7: Using ASN.1 with TTCN-3
Z.146
ES 201 873-8: Using IDL with TTCN-3
ES 201 873-9: Using XML with TTCN-3
ES 201 873-10: Using C/C++ with TTCN-3 (planned)
ITU-T Study Group 17, Geneva, 5-14 October 2005
12
Concepts
ITU-T
o Black-Box Testing with TTCN-3
o Test Configuration
o Test Components
o Communication Ports
o Test Verdicts
o Ingredients of TTCN-3
o Structure of TTCN-3 specs
o Re-use of existing Code
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
13
Black-box testing with TTCN-3
ITU-T
TTCN-3 Test Case
Port.send(Stimulus)
Port.receive(Response)
• Assignment
of a
Test Verdict
Port
System Under Test
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
14
Test configuration
1(2)
ITU-T
SUT
TTCN-3 Test Case
create
start
TC
create
start
12 October 2005
MTC
TC
TCs
create
start
ITU-T Study Group 17, Geneva, 5-14 October 2005
15
Test configuration
2(2)
ITU-T
Test System
IN
OUT
Connected Ports
TC2
TC1
OUT
IN
OUT
Mapped Ports
Abstract Test System Interface
OUT
IN
IN
Real Test System Interface
SUT
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
16
Test components
ITU-T
o There are three ‘kinds’ of components
• Abstract Test System Interface defined as
component
• MTC (Main Test Component)
• PTC (Parallel Test Component)
Test System
MTC
PTC1
PTC2
PTCn
Abstract Test System Interface
Real test system connected to the SUT
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
17
Communication ports 1(2)
ITU-T
o Test components communicate via ports
o A test port is modeled as an infinite FIFO queue
o Ports have direction (in, out, inout)
o There are three types of port
• message-based, procedure-based or mixed
TC1
P1.send (Msg)
12 October 2005
P1 (out)
P2 (in)
TC2
P2.receive (Msg)
ITU-T Study Group 17, Geneva, 5-14 October 2005
18
Language
Communication ports 2(2)
ITU-T
call
getcall
Callee
Caller
getreply
or
catch exception
reply
or
raise exception
blocking
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
blocking
19
Test verdicts
ITU-T
o Test verdicts: none < pass < inconc < fail < error
o Each test component has its own local verdict,
which can be set (setverdict) and read
(getverdict).
o A test case returns a global verdict
Verdict returned by the test case
when it terminates
P
FI
MTC
F
setverdict(fail)
12 October 2005
PTC1
P
setverdict(pass)
ITU-T Study Group 17, Geneva, 5-14 October 2005
PTCN
I
setverdict(inconc)
20
Ingredients of TTCN-3
ITU-T
o Built-in and user-defined generic data
TTCN-3
Data Types
Test Data
Test
Configuration
Test Behavior
types (e.g., to define messages,
service primitives, information
elements, PDUs).
o Actual test data transmitted/received
during testing.
o Definition of the components and
communication ports that are used to
build various testing configurations.
o Specification of the dynamic test
system behavior.
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
21
Structure of TTCN-3 specs –
TTCN-3 Modules
ITU-T
o Modules are the building
Module
blocks of all TTCN-3 test
specifications.
o A test suite is a module.
Module
Definitions
o A module has a
Module
Control
o Modules can be
definitions part and an
(optional) control part.
parameterized.
o Modules can import
definitions from other
modules.
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
22
Structure of TTCN-3 specs –
Module definitions part
ITU-T
Data Types
Constants
Signatures
Data Templates
Signature Templates
Communication Ports
Test Components
Functions
o Definitions are global to the
entire module.
o Data Type definitions are
based on TTCN-3 predefined
and structured types.
o Templates define the test
data.
o Ports and Components are
used in Test Configurations.
o Functions, Altsteps and Test
Cases define behavior.
Altsteps
Test Cases
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
23
Structure of TTCN-3 specs –
Module control part
1(2)
ITU-T
o Module control is the
Module
Module
Definitions
Module
Control
‘dynamic’ part of a TTCN-3
specification where the
test cases are executed.
o Local declarations, such as
variables and timers may
be made in the control
part.
o Basic programming
statements may be used to
select and control the
execution of the test
cases.
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
24
Structure of TTCN-3 specs –
Module control part
2(2)
ITU-T
module … {
…
control{
var integer count;
if(execute(SIP_UA_REC_V_001()) == pass) {
// Execute test case 10 times
count := 0;
while( count <= 10) {
execute(SIP_UA_REC_V_002());
count := count + 1;
} // end while
} // end if
} // end control
} // end module
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
25
Reuse of existing code –
The import mechanism
1(2)
ITU-T
import
Library
Module 1
implicit import
of a definition
import
Main
Module
import
Library
Module 2
12 October 2005
Library
Module 3
o Main Module contains
the control part, which
specifies test suite
execution.
o Modules may reuse
required
definitions from other
explicit
(library) modules.
import o Implicit import of
definitions via chains of
imports is not allowed,
i.e., an explicit import
has to be added.
• Reason: A module
shall know all
modules which it
depends on.
ITU-T Study Group 17, Geneva, 5-14 October 2005
26
Reuse of existing code –
The import mechanism
2(2)
ITU-T
import form ModuleOne {
modulepar ModPar2;
type RecordType_T2
}
import from ModuleTwo
recursive {
testcase T_case
}
import from ModuleThree
all except {
template all
}
12 October 2005
o Import allows to import
• single definitions
• definitions of a certain
kind, and
• groups of definitions
from other modules.
o Definitions may be imported
recursively.
o If several definitions are
addressed, certain definitions
can be excluded by using an
except directive.
ITU-T Study Group 17, Geneva, 5-14 October 2005
27
Use of non–TTCN-3 code –
Language mapping
ITU-T
XML Spec.
:
:
TTCN-3
Module
XYZ Spec.
ASN.1
XML
:
XYZ
12 October 2005
language
mapping
:
Importing non TTCN-3
definitions requires a
language mapping onto
TTCN-3.
o The language mapping
defines the meaning of non
TTCN-3 definitions in
TTCN-3 modules.
o The language mapping may
provide TTCN-3 additional
features for imported
definitions (e.g.,
operations for ASN.1 data
types).
o
import
ASN.1 Spec.
TTCN-3
ITU-T Study Group 17, Geneva, 5-14 October 2005
28
Table of contents
ITU-T
12 October 2005
1. Overall view of TTCN-3
2. TTCN-3 en detail
a. Types and values
b. Behavior specification
3. Implementation of TTCN-3
4. Presentation formats
5. Final remarks
ITU-T Study Group 17, Geneva, 5-14 October 2005
29
Language
Data types and test data –
Constants, types, templates
ITU-T
Data Types
Constants
Signatures
Data Templates
Signature Templates
Communication Ports
Test Components
Functions
Altsteps
Test Cases
12 October 2005
1(2)
o TTCN-3 data types:
• integer, char, universal char,
float, boolean, objid
• enumerated
• bitstring, hexstring,
octetstring, charstring,
universal charstring,
• record, record of, set, set
of, union
• anytype
• verdicttype
• address
o Useful types
• IEEE754float, long, byte, …
• Iso8859string, utf16string, …
ITU-T Study Group 17, Geneva, 5-14 October 2005
30
Language
Data types and test data –
Constants, types, templates
2(2)
ITU-T
const integer int_Const := 7;
external const boolean bool_Const;
// Normal constant
// External constant
type record Request { // Structured type definition
RequestLine
requestLine,
ReqMessageHeader reqMessageHeader optional,
charstring
crlf,
charstring
messageBody optional
}
template Request Invite := { // template for the Request type
requestLine
:= Request_Line("INVITE"),
reqMessageHeader := Req_Mes_Header("INVITE"),
crlf
:= ?,
messageBody
:= omit
}
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
31
Language
Encoding of Messages –
Attributes
1(2)
ITU-T
o Attributes can be assigned to all
Language Element
kinds of definitions, groups and
modules.
o Kinds of attributes
• Encoding information
• encode – attribute
• variant – attribute
• Values are standardized for ASN.1
encoding
• Presentation information
Attributes
• display – attribute
• Values are standardized for the
graphical and tabular presentation
format.
• User-defined
• extension - attribute
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
32
Language
Encoding of Messages –
Attributes
2(2)
ITU-T
group MyPDUs {
type record MyPDU1 { … }
group MySpecialPDUs {
type record MyPDU3 { … }
with {extension "MyVerySpecialRule"}
type record MyPDU4 { … }
}
with {extension "MySpecialRule"}
}
with {
display "PDU";
extension "MyRule"
}
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
33
Table of contents
ITU-T
12 October 2005
1. Overall view of TTCN-3
2. TTCN-3 en detail
a. Types and values
b. Behavior specification
3. Implementation of TTCN-3
4. Presentation formats
5. Final remarks
ITU-T Study Group 17, Geneva, 5-14 October 2005
34
Language
ITU-T
Specifying test behavior –
Alternative behavior 1(2)
o … has to be specified whenever test component is ready to
take a response from the SUT or a timeout.
o … is typically defined by several alternatives, which
• are evaluated according to their appearance
• may be guarded
• can be part of an altstep, which may be called
explicitly or activated as default.
o … forks the test behavior (the typical „tree“), but in
TTCN-3 alternatives can be joined again after the end of
an alternative behavior.
o All other cases can be handled in an else branch.
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
35
Specifying test behavior –
Alternative behavior 2(2)
Language
ITU-T
alt {
[] L1.receive(MyMessage1) {
:
// do something
}
[x>1]
L2.receive(MyMessage2) {}
[x<=1] L2.receive(MyMessage3) {}
[]
MyAltstep;
[else] stop
// call of a altstep
// else branch
}
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
36
Language
ITU-T
Specifying test behavior –
Interleaved behavior
o Shorthand for all alternative
permutations
• All messages must be received, but in
any order
interleave {
[] PCO1.receive(MyMessageOne) {}
[] PCO1.receive(MyMessageTwo) {}
[] PCO1.receive(MyMessageThree) {}
}
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
37
Table of contents
ITU-T
12 October 2005
1. Overall view of TTCN-3
2. TTCN-3 en detail
a. Types and values
b. Behavior specification
3. Implementation of TTCN-3
4. Presentation formats
5. Final remarks
ITU-T Study Group 17, Geneva, 5-14 October 2005
38
Overview –
The TTCN-3 test system
ITU-T
T e s t S ys te m Us e r
TM
CD
CH
TCI
TE
TRI
SA
o
o
o
o
o
o
o
TE – TTCN-3 Executable
SA – System Adapter
PA – Platform Adapter
CD – Coder/Decoder
TM – Test Management
CH – Component Handling
SUT – System Under Test
PA
S UT
ETSI ES 201 873-1: TTCN-3 Core Language
ETSI ES 201 873-5: TTCN-3 Runtime Interface (TRI)
ETSI ES 201 873-6: TTCN-3 Control Interfaces (TCI)
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
39
Overview –
Implementing TTCN-3
ITU-T
TE
TTCN-3
Executable
compile
Abstract Test Suite
+
SUT
build
TTCN-3 Runtime System
Executable Test Suite
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
40
Table of contents
ITU-T
12 October 2005
1. Overall view of TTCN-3
2. TTCN-3 en detail
a. Types and values
b. Behavior specification
3. Implementation of TTCN-3
4. Presentation formats
5. Final remarks
ITU-T Study Group 17, Geneva, 5-14 October 2005
41
TTCN-3 presentation formats –
Overall view
ITU-T
ASN.1
Types &
Values
TTCN-3
Core
Notation
Tabular
Format
Other
IDL Types
& Values 2
Graphical
Format
Other
XMLTypes
& Values 3
Other Types
C/C++
& Values n
12 October 2005
TTCN-3
User
Presentation
UML
Format n
Testing
Profile
ITU-T Study Group 17, Geneva, 5-14 October 2005
42
The graphical presentation
format of TTCN-3
ITU-T
testcase
Page 1(2)
MyTestCase
(in
boolean internetService,
inout integer nrPass)
runs on MtcType system TestSystemtype
mtc
P1
mPCOtype
MtcType
CP
mCPtype
var reportType report
var default def
:= activate
(MyDefault())
map(self:P1,
System:mPCO)
if (internetservice)
newInternetPTC()
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
43
U2TP – A test case
Data partition
ITU-T
sd invalidPIN
{readOnly} Integer invalidPIN; { current.isPinCorrect(invalidPIN) == false }
«sut»
atm
hwe
Setting a
timer
current
Stimulus
storeCardData(current)
Stopping
a timer
t1(2.0)
display(”Enter PIN”)
Observation
t1
isPinCorrect(invalidPIN)
Duration
constraint
{0 .. 3}
isPinCorrect(invalidPIN)
isPinCorrect : false
isPinCorrect : false
display(”Invalid PIN”)
Setting
arbitrated
verdict
12 October 2005
display(”Enter PIN again”)
Function
return value
«validationAction»
pass
ITU-T Study Group 17, Geneva, 5-14 October 2005
44
Table of contents
ITU-T
12 October 2005
1. Overall view of TTCN-3
2. TTCN-3 en detail
a. Types and values
b. Behavior specification
3. Implementation of TTCN-3
4. Presentation formats
5. Final remarks
ITU-T Study Group 17, Geneva, 5-14 October 2005
45
Managing TTCN-3 projects –
Potential usage
1(2)
ITU-T
o Applicability for
different test phases
• Host/target tests
• System integration and
system test
• User acceptance test
o Features required for a
test automation solution
• Test design (low-level,
high-level, graphical)
• Scheduling of test runs
• Centralized/distributed
test runs
• Log/trace analysis
• Test case management
• Support of standards
12 October 2005
Legend for the table on
next slide
• … feature must be
supported in this test
phase
• ()… feature should be
supported
•
fully colored field…
feature supported by
TTCN-3
•
hatched colored field…
feature partly supported
by TTCN-3
ITU-T Study Group 17, Geneva, 5-14 October 2005
46
Managing TTCN-3 projects –
Potential usage
2(2)
ITU-T
Requirement
Low-level test design
(programming level)
Host
Test
Target
Test
System
Integr.
System
Test


()
()







()




()




High-level test design
(textual)
Graphical test design and
test result analysis
Scheduling of test runs / test
resource management
Centralized test execution

Distributed test execution

Log / trace file analysis
Test case management
(including version control)
Support of ASN.1 and
standardized test suites
12 October 2005

User
Accept.







()
ITU-T Study Group 17, Geneva, 5-14 October 2005
47
TTCN-3 extensions
Work items in standardization
ITU-T
o Language extensions
mechanisms
• Packages and profiles
o Extended
communication
mechanisms
• Broadcast / multicast
(edition 3.0.0)
• Synchronization /
coordination (edition
3.0.0)
12 October 2005
o Real-time extensions
• Absolute time support
• Time-constrained
operations
o Better performance
testing support
• Implicit test configuration
• Implicit communication
• Performance measurement
ITU-T Study Group 17, Geneva, 5-14 October 2005
48
Current TTCN-3 tool providers
ITU-T
o Tool providers
•
•
•
•
•
•
Danet
DaVinci Communication
Open TTCN
Telelogic
Testing Technologies
Strategic Test Solutions
o Internal tools used by
• Nokia
• Ericsson
• Motorola
12 October 2005
o Existing test devices with
TTCN-3 support
(for telecommunication
applications)
• Alcatel A1100
• Navtel InterWatch
• Nethawk
• Tektronix G20
ITU-T Study Group 17, Geneva, 5-14 October 2005
49
Conclusions
ITU-T
o TTCN-3 finds its way into practice
o Lots of interest from industry and academia
o Mature TTCN-3 standard
o Stimulates further research & development
• New application domains, e.g. automotive
• Real-time and performance testing
• Test patterns
o Still possibilities to shape the future TTCN-3
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
50
Acknowledgement
ITU-T
o Slides are based on a TTCN-3 Tutorial from
Grabowski and Ulrich
o Prof. Dr. Jens Grabowski
• Institute for Informatics, University of
Göttingen
• Is in the TTCN-3 business since the beginning
o Dr. Andreas Ulrich
• Is a Principal Engineer at Siemens’ Corporate
Technology Division in München, Germany
• Member of the ETSI TTCN-3 maintenance
group
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
51
International Telecommunication Union
An Introduction
to
version 3
Dr. Michael Ebner
University Göttingen, Germany
ebner@cs.uni-goettingen.de
ITU-T Study Group 17, Geneva, 5-14 October 2005
International Telecommunication Union
Literature on TTCN-3
Standard documents
Overview articles
Graphical presentation format
TTCN-3 control and runtime interface
IDL to TTCN-3 mapping
TTCN-3 real-time extensions
UML Testing Profile
ITU-T Study Group 17, Geneva, 5-14 October 2005
Literature on TTCN-3
ITU-T
1(6)
o Standard documents: (can be found on the TTCN-3 homepage:
http://www.ttcn3.org/ or
http://www.etsi.org/ptcc/ptccttcn3.htm)
•
•
•
•
•
•
•
•
•
•
ES 201 873-1: TTCN-3 Core Language
ES 201 873-2: TTCN-3 Tabular Presentation Format (TFT)
ES 201 873-3: TTCN-3 Graphical Presentation Format (GFT)
ES 201 873-4: TTCN-3 Operational Semantics
ES 201 873-5: TTCN-3 Runtime Interface (TRI)
ES 201 873-6: TTCN-3 Control Interface (TCI)
ES 201 873-7: Using ASN.1 with TTCN-3
ES 201 873-8: Using IDL with TTCN-3
ES 201 873-9: Using XML with TTCN-3
ES 201 873-10: Using C/C++ with TTCN-3 (planned)
o Example test suites:
• See: http://www.etsi.org/ptcc/ptccttcn3.htm
• E.g., http://www.etsi.org/ptcc/ptccsip_osp.htm
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
54
Literature on TTCN-3
ITU-T
o
2(6)
Overview articles
• Jens Grabowski, Dieter Hogrefe, György Réthy, Ina Schieferdecker,
Anthony Wiles, Colin Willcock. An introduction into the testing and
test control notation (TTCN-3). Computer Networks, Volume 42,
Issue 3, Elsevier, Amsterdam, Juni 2003, 375-403.
• Jens Grabowski, Anthony Wiles, Colin Willcock, Dieter Hogrefe. On
the Design of the new Testing Language TTCN-3. '13th IFIP
International Workshop on Testing Communicating Systems'
(Testcom 2000), Ottawa, 29.8.2000-1.9.2000, Kluwer Academic
Publishers, August 2000.
o
Graphical presentation format
• P. Baker, E. Rudolph, I. Schieferdecker. Graphical Test Specification
- The Graphical Format of TTCN-3. Proc. of the 10th SDL Forum
2001, Copenhagen, June 2001.
• E. Rudolph, I. Schieferdecker, J. Grabowski: HyperMSC - a
Graphical Representation of TTCN. Proc. of the 2nd Workshop of
the SDL Forum, Society on SDL and MSC, Grenoble, June 2000.
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
55
Literature on TTCN-3
ITU-T
o
3(6)
TTCN-3 control and runtime interface
• S. Schulz, T. Vassiliou-Gioles. Implementation of TTCN-3 Test
Systems using the TRI. Testing Internet Technologies and Services The IFIP 14th International Conference on Testing of
Communicating Systems March, 19th - 22nd, 2002, Berlin, Kluwer
Academic Publishers, March 2002.
• I. Schieferdecker, T. Vassiliou-Gioles. Realizing distributed TTCN-3
test systems with TCI. IFIP 15th Intern. Conf. on Testing
Communicating Systems - TestCom 2003, Cannes, France, May 2003.
o
IDL to TTCN-3 mapping
• M. Ebner, A. Yin, M. Li. A Definition and Utilisation of OMG IDL to
TTCN-3 Mappings. TestCom 2002: Testing Internet Technologies and
Services - The IFIP 14th International Conference on Testing of
Communicating Systems March, 19th - 22nd, 2002, Berlin, Kluwer
Academic Publishers, March 2002.
o
12 October 2005
XML to TTCN-3 mapping
• I. Schieferdecker, B. Stepien. Automated Testing of XML/SOAP
based Web Services. Proceedings of the 13. Fachkonferenz der
Gesellschaft für Informatik (GI) Fachgruppe "Kommunikation in
verteilten Systemen" (KiVS), Leipzig (Germnay), Febr. 26th-28th,
2003.ITU-T Study Group 17, Geneva, 5-14 October 2005
56
Literature on TTCN-3
ITU-T
12 October 2005
4(6)
o TTCN-3 real-time extensions
• Zhen Ru Dai, Jens Grabowski, Helmut Neukirchen. Timed TTCN3 - A Real-Time Extension for TTCN-3. TestCom 2002: Testing
Internet Technologies and Services -- The IFIP 14th International
Conference on Testing of Communicating Systems March, 19th 22nd, 2002, Berlin, Kluwer Academic Publishers, March 2002.
• Zhen Ru Dai, Jens Grabowski, Helmut Neukirchen. TimedTTCN-3
Based Graphical Real-Time Test Specification. Testing of
Communicating Systems (Editors: D. Hogrefe, A. Wiles).
Proceedings of the 15th IFIP International Conference on Testing
of Communicating Systems, Sophia Antipolis, France, May 2003.
LNCS 2644, Springer, May 2003.
• Helmut Neukirchen, Zhen Ru Dai, Jens Grabowski.
Communication Patterns for Expressing Real-Time
Requirements Using MSC and their Application to Testing.
Testing of Communicating Systems. Proceedings of the 16th IFIP
International Conference on Testing of Communicating Systems,
Oxford, UK, March 2004. LNCS 2978, Springer, March 2004.
ITU-T Study Group 17, Geneva, 5-14 October 2005
57
Literature on TTCN-3
ITU-T
12 October 2005
5(6)
o UML Testing Profile
• Online Resources: http://www.fokus.gmd.de/u2tp/
• U2TP consortium. UML 2.0 Testing Profile Specification. OMG
Adopted Specification ptc/03-08-03. (for download see:
http://www.fokus.gmd.de/u2tp/)
• Zhen Ru Dai, Jens Grabowski, Helmut Neukirchen, Holger Pals.
From Design to Test with UML - Applied to a Roaming Algorithm
for Bluetooth Devices. Testing of Communicating Systems.
Proceedings of the 16th IFIP International Conference on Testing
of Communicating Systems (TestCom2004), Oxford, United
Kingdom, March 2004. LNCS 2978, Springer, March 2004.
• Ina Schieferdecker, Zhen Ru Dai, Jens Grabowski, Axel Rennoch.
The UML 2.0 Testing Profile and its Relation to TTCN-3. Testing
of Communicating Systems (Editors: D. Hogrefe, A. Wiles).
Proceedings of the 15th IFIP International Conference on Testing
of Communicating Systems (TestCom2003), Sophia Antipolis,
France, May 2003. LNCS 2644, Springer, May 2003, pp. 79-94.
ITU-T Study Group 17, Geneva, 5-14 October 2005
58
Literature on TTCN-3
ITU-T
6(6)
o UML Testing Profile (cont.)
• Paul Baker, Zhen Ru Dai, Jens Grabowski, Øystein Haugen, Serge
Lucio, Eric Samuelsson, Ina Schieferdecker, Clay Williams. The
UML Testing Profile. Proceedings of the 'Conference on Quality
Engineering in Software Technology 2004' (CONQUEST 2004) in
Nuremberg (Germany), September 22-24, 2004 .
o Further resources
• More can be found in the proceedings of the
TestCom conferences and on the homepages of the
TTCN-3 team members (e.g., I. Schieferdecker
and J. Grabowski) and the TTCN-3 tool providers.
12 October 2005
ITU-T Study Group 17, Geneva, 5-14 October 2005
59