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 Tel.: +48 663 426 716,Agenda,Introduction Step 1 Without TTCN-3 Step 2 New test environment with TTCN-3 Step 3 Make te
2、sting easy Step 4 Our future,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,Step 1 Without TTCN-3,Only one protocol (SIP) Very basic scenarios Simple environment Sim
3、ple matching mechanism,Simple environment,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,?,Second protocol,Test team problems,Preparation for the test execution Exchanging information between
4、traffic generators No flexibility Poor matching mechanism Code reuse Message synchronisation Verification of correct message sequence Timers,Solution,We need something completely different. So lets try TTCN-3,Step 2 New test environment with TTCN-3,Ro (online charging) Rf (offline charging),IMS AS,M
5、GW,P-CSCF,S-CSCF,I-CSCF,HSS,MGCF,CSCF,PSTN/PLMN,other SIP network,CSCF,SIP,SIP,SIP,Charging,Diameter,MRFP,H.248,Provisioning,LDAP,Voice & Video mail,SIP,Cx,CM,PM,Muta,ISC,LDAP,Mp,Audio & Video Announcements Audio & Video Conference,SBG,SIP,SIP NNI or H.323,Sh,Diameter/TCP,SLF,Dh,Diameter/TCP,CAI3G/X
6、CAP,Dx,Px App,Px,MRFC,Mr,SIP,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,Function Test Environment,Sh (Diame
7、ter),Rf (Diameter),MP (H.248),Dh (Diameter),MTAS,ISC (SIP),Ro (Diameter),TTCN-3,CAI3G/ Ut (XCAP),Muta (LDAP),Basic call setup vs. Test simulation,Primary CCF,New test team problems,Testing is time consuming Development of test cases difficult to learn Lots of code to write for one test case Test exe
8、cution quite complex,Solution,We need a good testFramework and Automation,Step 3 Make testing easy,TTCN-3 function library & API Creation and initialization of test components, routing ofmessages and verification of message contentTest automation scripts Run before and after the TC call flow. Ensure
9、s test environment integrity and checks for problems caused by TC execution.,Directory Structure,Messages exchange on ports between the SUT and the Framework components (defaults used),5060 ISC1,SIP_DISPATCHER_CT,5061 ISC2,CSCF (SIP dispatcher),Framework component overview,Non-Session,Dispatchers us
10、es list of keys to differientiate sessions,Non-Session,Sip caller and callee are together a SIP session,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 tran
11、sparently and automatically Simplifies TC maintenance and development New checks can be added automatically to existing TCs via the framework,Framework benefits,Majority of TCs automated Full automated regression test Flexibility in test case creation User friendly,Examples of automated test activit
12、ies,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,Step 4 Our future,Environment very flexible to test new features required by customers Smart way of regression testing More testing in shorter time,Damian Zolich, TTCN-3 User Conference 2011 Ericpol Telecom Sp. z o.o. 7 9 June 2011 - Bled, Slovenia Tel.: +48 663 426 716,Thank you,
