V. P. Singh, A. Rauland, A. Ulrich, and Z. Chao, "Multi site testing strategy using TTCN-3," ETSI TTCN-3 User Conference 2007: Stockholm (Sweden), May 29-June 1, 2007.
Added by: Deleted user (01 Aug 2008 14:04:01 Europe/Berlin) Last edited by: Deleted user (20 Aug 2008 11:44:47 Europe/Berlin)
|Resource type: Conference Paper
BibTeX citation key: Singhb
View all bibliographic details
Creators: Chao, Rauland, Singh, Ulrich
Publisher: Ericsson, ETSI (Stockholm (Sweden))
Collection: ETSI TTCN-3 User Conference 2007
Views index: %
Popularity index: 11.5%
The presentation discusses a testing strategy using TTCN-3 that has proven its excellence in a very vast and widely distributed project. We have realized the advantages of using TTCN-3 for testing in the telecommunication domain and have been using it massively for the last 3 years. The project that is taken as a baseline for this presentation is currently running at 4 different locations across the world. The major challenge is to work out a testing technique that can be easily maintained and synchronised across all sites.
For this purpose we realised the need of developing various tools and middle wares mainly in TTCN-3 and Java (however other languages are also used) and maintaining them centrally.
We are testing parts of the UMTS Radio Network Controller (RNC), which is a very complex system making our test system also pretty complex. The complete testing process is based on the TTCN-3 test language and comprises of various phases that are host testing, blade testing, and integration testing.
The testing starts with the identification of the test purposes, followed by the derivation of test case specifications in the form of specialized Message Sequence Charts (MSCs), which are written by domain experts. These specifications are then given to test scripters who produce executable TTCN-3 scripts in turn. The scripts are finally compiled and executed to test the SUT.
All test scripters at the different sites use a test middleware called TcSkeleton that is developed and maintained centrally. This middleware is a library of functions written in TTCN-3 that implements algorithms to handle the common behaviour of the test system. The middleware simplifies the task of the scripter massively in converting a test MSC into executable TTCN-3 scripts and helps him focussing on the correct translation of the test specification instead of spending time on implementing the test execution logic.
In this presentation, it is also described how the work load across different geographically distributed sites is shared and how TTCN-3 helps us in exchanging intermediate test artefacts. In general it describes our experiences with TTCN-3 and elaborates our strategy towards successful testing.
Added by: Deleted user Last edited by: Deleted user