Automated Target Testing with TTCN-3: Experiences from WiMAX Call - - PowerPoint PPT Presentation

automated target testing with ttcn 3 experiences from
SMART_READER_LITE
LIVE PREVIEW

Automated Target Testing with TTCN-3: Experiences from WiMAX Call - - PowerPoint PPT Presentation

Automated Target Testing with TTCN-3: Experiences from WiMAX Call Processing Features By Bhaskar Rao G Srinath Y Sridhar Y Jitesh M Motorola India Pvt Ltd, Hyderabad bhaskarraog@motorola.com 23 November 2009 T3UC-2009 1 Agenda


slide-1
SLIDE 1

Automated Target Testing with TTCN-3: Experiences from WiMAX Call Processing Features

23 November 2009 T3UC-2009 1

By

Bhaskar Rao G Srinath Y Sridhar Y Jitesh M Motorola India Pvt Ltd, Hyderabad bhaskarraog@motorola.com

slide-2
SLIDE 2

Agenda

  • What is WiMAX
  • WiMAX deployment and architecture
  • ASNGW Decision Point feature architecture
  • Test set-up for DP testing
  • Motivation for TTCN-3
  • Automation framework

23 November 2009 T3UC-2009 2

  • Feature Testing Strategy
  • Test system details
  • Test Execution set-up
  • Challenges faced
  • Benefits
  • Take-away
  • Conclusions
slide-3
SLIDE 3

WiMAX

  • Standards based technology - IEEE

802.16e

  • Superior Performance – 75Mbps of

throughput

  • Scalable channel bandwidths - 12.5 to

23 November 2009 T3UC-2009 3

  • Scalable channel bandwidths - 12.5 to

20MHz

  • Mobility of subscribers in the network

coverage is supported for speeds ranging between 60kmph to 120 kmph

  • Audio/Video streaming during mobility
slide-4
SLIDE 4

ASN GW DP EP

AP AP AP

Internet

AAA DHCP

WiMAX: Deployment

23 November 2009 T3UC-2009 4

ASN GW DP EP ASNG W DP EP

AP AP AP AP

Access Service Network

CPE CPE IP Connected HA Connectivity Service Network

slide-5
SLIDE 5

WiMAX Reference Architecture

23 November 2009 T3UC-2009 5

slide-6
SLIDE 6

ASNGW: Decision Point

  • Decision Point runs on ATCA chassis
  • HA design
  • Provides Authentication and Authorization for

SS

23 November 2009 T3UC-2009 6

SS

  • Mobility management for SS
  • Connectivity management with Access

Points, FA/Router and other neighboring ASNGWs

  • Confirming to NWG standard
slide-7
SLIDE 7

ASNGW Decision Point: Feature Architecture

  • 23 November 2009

T3UC-2009 7

  • Other Boxes
slide-8
SLIDE 8

WiMAX ASNGW Test Setup

  • 23 November 2009

T3UC-2009 8

  • Simulated AP[

1..n]

  • !

"#$ The proprietary tool supports test scripts

Simulates other NEs

slide-9
SLIDE 9

Motivation for TTCN-3

  • Component testing and applicable beyond
  • Standard language for test specification
  • Rich Language features to meet testing needs of

WiMAX features

  • Tool support through –Tau G2 Tester
  • Good automation support and ready made

23 November 2009 T3UC-2009 9

  • Good automation support and ready made

framework

  • Regression capabilities
  • Automated testing without need for re-compilation
  • Verdict handling
  • Automated logging with failure reasons
  • Command line execution, compilation and

generation

  • Dynamic logging
slide-10
SLIDE 10

Automation framework

Reused SA and PA Runtime Library

Mousetrap tool

TTCN-3 data types Encoder/decoder Message specifications External C code Test Cases SDs and UCDs conversion

23 November 2009 T3UC-2009 10

Test System TAU Tester C Compiler

TS Executable

TTCN-3 data types Dummy templates Port definitions Generated code

slide-11
SLIDE 11

Feature Testing Strategy

TTCN-3 Base Framework Feasibility for a componet

REUSE

REUSE

23 November 2009 T3UC-2009 11

NWG 1.1

slide-12
SLIDE 12

Test system architecture

TTCN-3 MTC and PTC (0..N) TCP/IP (IPC) Code Encoder Decoder Log Mechanism

SUT

23 November 2009 T3UC-2009 12

Runtime Library

Test System (TS)

Hand code Auto code

slide-13
SLIDE 13

Test Specification

  • %

& '&#&( ) )

  • )

"%*+ "%*+

  • ,
  • -..
  • -..
  • 23 November 2009

T3UC-2009 13

/ / , 00"%*+ 00"%*+ 00*+ 00*+ / / , 00"%*+ 00"%*+ 00*+ 00*+ ,00*+ ,00*+

,

slide-14
SLIDE 14

Sample Test case

type component MTCType { port RADIUS_INTERFACE_type mtcPort_RADIUS_INTERFACE; port ApAsngw_type mtc_ap_asngw_port ; timer T; } type component TSI { port RADIUS_INTERFACE_type tsiPort_RADIUS_INTERFACE ; 23 November 2009 T3UC-2009 14

testcase TC1 (integer configParams) runs on MTCType system TSI { //variables declaration // mapping of ports mtcPort_.send(AUTH_MyTemplate); alt { []mtcPort_auth_.receive(EAP_REQ_MyTemplate) -> value eap_req_var { mtcPort_auth_.send(EAP_RSP_MyTemplate_PAR(eap_req_var)) alt { ....... }

port RADIUS_INTERFACE_type tsiPort_RADIUS_INTERFACE ; port ApAsngw_type tsi_mtc_ap_asngw_port ; }

slide-15
SLIDE 15

Test Execution set-up

ASNGW (SUT) Env

Internal communication

Target Database

23 November 2009 T3UC-2009 15

Proxy TTCN-3 Test System (AP, AAA)

communication

Linux-box

slide-16
SLIDE 16

Challenges faced

  • SUT testing
  • Health-check integration
  • Integration of encryption algorithm
  • Supporting various test configurations
  • Communication aspects

– Integration with proprietary paradigm

23 November 2009 T3UC-2009 16

– Integration with proprietary paradigm

  • Issues pertaining to integration of shared memory

– Population of shared memory

  • Issues pertaining to real-time nature of the application

– When full log is enabled, reboots – Controlling of response timers

slide-17
SLIDE 17

Benefits

  • Standard language for testing
  • Automation capabilities
  • Reuse

– Results of one feature testing have helped the usage and extension to the other features.

23 November 2009 T3UC-2009 17

– The test architecture and reuse of the test system across various features

  • Ability of TTCN-3 to handle configuration,

execution and tracing of test case execution

  • Better cycle time, quality and productivity
slide-18
SLIDE 18

Take-away

  • Organizations which are not using TTCN3

– Technology is good for any message based testing – For API based testing, need to investigate synchronous communication

  • Organizations which are using TTCN3

23 November 2009 T3UC-2009 18

  • Organizations which are using TTCN3

– Development of common TTCN-3 framework – Automation of test system components

  • Research organizations and tool vendors

– Automation support may be provided by the vendors

  • Automatic generation of encoders/decoders, templates,

communication parts

  • Thoughts on …Domain specific common test framework
slide-19
SLIDE 19

Conclusions

  • TTCN-3 approach is flexible to adopt to various

features and testing of components independently

  • Automation of TTCN-3 test system components
  • Reuse of Message specifications across SUT

and TS

23 November 2009 T3UC-2009 19

and TS

  • Reuse of framework across test phases
  • Good cycle time reduction to market, higher

quality and greater productivity

  • Challenges will be there to address

– Ex: Encryption algorithms etc

slide-20
SLIDE 20

Q&A

23 November 2009 T3UC-2009 20

Q&A