wu new ttcn-3 test adapter framework with capability ... 1/session 2/wu...new ttcnnew ttcn- ---3...

New TTCNNew TTCNNew TTCNNew TTCN----3 Test Adapter Framework 3 Test Adapter Framework 3 Test Adapter Framework 3 Test Adapter Framework with Capability Descriptionwith Capability Descriptionwith Capability Descriptionwith Capability Description

Yang LIUBei Hang University

Outline

• Introduction• The Problem• The solution• The solution• Test Adapter Framework• Evaluation• Conclusions

The separation of test specification with test adapter

TM: Management

Test System User

TCI

Introduction

System Under Test (SUT)

SA (System Adapter) PA (Platform Adapter)

CH:

Component

Handling

CD: CodecTE

TCI

TRI

Outline

• Introduction• The Problem• The solution• The solution• Test Adapter Framework• Evaluation• Conclusions

The Problem

• The dependencies among the abstract test

case, CD and adapters (SA and PA) are

obvious.

• There is no explicit semantic definition of the • There is no explicit semantic definition of the

dependencies in TTCN-3 standard so far.

Outline

• Introduction• The Problem• The solution• The solution• Test Adapter Framework• Evaluation• Conclusions

The solution

• Capability description language for specifying

the dependencies among the abstract test

case, CD, SA and PA

• A Test Adapter Framework• A Test Adapter Framework

– Automatic load the Adapter which comply with

the requirements of test cases

– Based on the description language

– Transparent to the test system

Outline

• Introduction• The Problem• The solution• The solution• Test Adapter Framework• Evaluation• Conclusions

Mapping between the Adapter and

TestCase

• Adapter Capacity

– SA： Communication Adapter

– PA： External method Adapter

– CD（ECD）： Data Adapter

AdapterAdapter Capacity

– CD（ECD）： Data Adapter

• Test System Interface(TSI)’s demand

– Demand for communications capacity

– Demand for External method

– Input and output data types SUTTSI’s

demand

Adapter Framework – Overall

Architecture

Function Layer

Adapter

1

Adapter

2……

Adapter

N

Test Adapter Framework

TE

SUT

Execute Engine

Configuration Layer

Configuration

ManagementSwitcher

Interactive Layer

SA PA CD

Adapter Framework – Switcher

SAs PAs CDs

Test Adapter Switcher

Loader Mapper Selector

Adapter Framework - Loader

• Environment Description– OS

– Environment VarsTest

Adapter (jar)

Loader Adapter

Objects

• Test Adapter Description – SA

– PA

– CD

Test Adapter 1

Attributes

Test Adapter 2

Attributes

Test Adapter n

Attributes

Environment

Abilities

…

Adapter Framework - Mapper

TSI SA

port name

type

name

port-type

SA

(jar)

PA

CD

type

module

Encode

Rules

module

name

rule

name

PA

(jar)

CD

(jar)

example of capability matching

capability requirement description of the test case:

capability provision description of the CD & SA :

Adapter Framework – Selector

Dynamic switcher

• Prerequisite :– TTCN-3 test script

– SA , PA & CD

– Test adapter & TSI ‘s Description File

descAdapter load mapping relationship

jardesc

Test adaptor Description File

Adapter load

Loader

mapping relationship

MapperMapping object

Select Adapter

TE Selector

Specificadapterobject

Adapter Object

Outline

• Introduction• The Problem• The solution• The solution• Test Adapter Framework• Evaluation• Conclusions

Evaluation

• Experiment:

• SUT

–Simulated heterogeneous distributed

systems

HTTP

• Test system

–SA and CD of Three test subsystems

–test script

• Support Tools

–Compiler (TTthree)

–Execution Engine (TTman)

SUT

TCP

UDP

Experiment with TAF

SUT TCP UDP HTTP

module TCPTest UDPTest HTTPTest

TSIPortName tcpSystemPort udpSystemPort httpPortArray

type TCP UDP HTTP

encodeRules TCPCodec UDPCodec HTTPCodec

SATCP_TA.jar

/TCPTestAdapterUDP_TA.jar

/UDPTestAdapterHTTP_TA.jar

/HTTPTestAdapter

CDTCP_Codec.jar

/TCPCodecUDP_Codec.jar

/UDPCodecHTTP_Codec.jar

/HTTPCodec

TAF –Test Result

Performance comparison

Outline

• Introduction• The Problem• The solution• The solution• Test Adapter Framework• Evaluation• Conclusions

Conclusions

• Why we design the test adapter framework

• Existing problems

– Test Adapter Framework configuration is complex

– The efficiency of loading the modules which will – The efficiency of loading the modules which will

be dynamic switching is low

Conclusions

• Future work

– Raise the ability to match to the semantic level

– Use a general language of Capability Description

– Set the general test adapter Standard – Set the general test adapter Standard

THANK YOU