The employment of TTCN-3 for testing the Application Server in the IMS network.

1
The employment of TTCN-3 for testing the
Application Server in the IMS network.

• Damian Zolich,
  TTCN-3 User
  Conference 2011
• Ericpol Telecom Sp. z o.o.
  7 9 June 2011 -
  Bled, Slovenia
• damian.zolich_at_ericpol.com
• Tel. [phone]

2
Agenda

• Introduction
• Step 1 Without TTCN-3
• Step 2 New test environment with TTCN-3
• Step 3 Make testing easy
• Step 4 Our future

3
Our environment in numbers

• About 7000 test cases
• Up to 80 components in one test case
• About 45 users
• 930 files
• 1,5 million code lines
• Support for 7 different protocols
• 11 interfaces

4
Step 1 Without TTCN-3

• Only one protocol (SIP)
• Very basic scenarios
• Simple environment
• Simple matching mechanism

5
Simple environment
6
New challenges

• New traffic generator (H.248)
• More and more complex scenarios
• New protocols in the near future
• More and more pressure on matching mechanism

7
Second protocol
?
8
Test team problems

1. Preparation for the test execution
2. Exchanging information between traffic generators
3. No flexibility
4. Poor matching mechanism
5. Code reuse
6. Message synchronisation
7. Verification of correct message sequence
8. Timers

9
(No Transcript)
10
Solution

• We need something completely different.
• So lets try TTCN-3

11
Step 2 New test environment with TTCN-3
Charging
SLF
Px App
Px
Ro (online charging) Rf (offline charging)
Dh
Diameter/TCP
Provisioning
Muta
Diameter
CM,PM
LDAP
CAI3G/XCAP
IMS AS
Mp
Mr
H.248
LDAP
MRFP
Audio Video Announcements Audio Video
Conference
Sh
SIP
Diameter/TCP
ISC
SIP
MRFC
Voice Video mail
S-CSCF
Cx
HSS
SIP
MGW
I-CSCF
Dx
SIP
MGCF
PSTN/PLMN
SIP
P-CSCF
SIP
other SIPnetwork
CSCF
CSCF
SBG
SIP NNI or H.323
12
New challenges

• Test environment which enables
• Simulation of nodes around the Application Server
  
• Support of all required interfaces
• Support of all required protocols
• Support of advance matching mechanism
• Coordination between interfaces

13
Function Test Environment
Ro (Diameter)
Rf (Diameter)
Sh (Diameter)
Muta (LDAP)
Dh (Diameter)
MTAS
CAI3G/ Ut (XCAP)
ISC(SIP)
MP (H.248)
TTCN-3
14
Basic call setup vs. Test simulation
Primary CCF
15
New test team problems

1. Testing is time consuming
2. Development of test cases difficult to learn
3. Lots of code to write for one test case
4. Test execution quite complex

16
Solution

• We need a good test
• Framework and Automation

17
(No Transcript)
18
Step 3 Make testing easy

• TTCN-3 function library API
• Creation and initialization of test components,
  routing of
• messages and verification of message content
• Test automation scripts
• Run before and after the TC call flow.
• Ensures test environment integrity and checks for
  problems caused by TC execution.

19
Directory Structure
20
Messages exchange on ports between the SUT and
the Framework components (defaults used)
SIP_DISPATCHER_CT
5060 ISC1
5061ISC2
21
Framework component overview
Non-Session
CSCF (SIP dispatcher)
Sip caller and callee are together a SIP session
Non-Session
Dispatchersuses list of keys todifferientiate
sessions
22
Framework benefits

• Higher abstraction level for writing TCs
• More readable/understandable test cases written
  in a consistent style
• Complex and extensive common verification details
  are handled transparently and automatically
• Simplifies TC maintenance and development
• New checks can be added automatically to existing
  TCs via the framework

23
Framework benefits

• Majority of TCs automated
• Full automated regression test
• Flexibility in test case creation
• User friendly

24
Examples of automated test activities

• Pre execution activity
• cleaning environment
• checking environment
• run external applications (e.g. wireshark)
• Post execution activity
• collecting all logs into one archive file
• monitor for hanging processes, memory leaks
  system crashes

25
(No Transcript)
26
Step 4 Our future

• Environment very flexible to test new features
  required by customers
• Smart way of regression testing
• More testing in shorter time

27
(No Transcript)
28
Thank you

• Damian Zolich,
  TTCN-3 User
  Conference 2011
• Ericpol Telecom Sp. z o.o.
  7 9 June 2011 -
  Bled, Slovenia
• damian.zolich_at_ericpol.com
• Tel. [phone]