Sie sind auf Seite 1von 11

First Steps User’s Guide

TTsuite-ITS

This user’s guide helps you to download and install TTworkbench, and guides you through configuring and running test cases of TTsuite-ITS.

1. Requirements

2. Get TTworkbench and TTsuite-ITS

3. Installation

4. Configure the Cohda Box as Bridge

5. Start the Bridge Application

6. Start the Simulated SUT

7. Load Test Campaign

8. Configuration

9. Running Test Case

10. Details

11. Documents

12. Appendix

the Simulated SUT 7. Load Test Campaign 8. Configuration 9. Running Test Case 10. Details 11.

For a successful proceeding please follow the instructions step by step!

If you need any assistance or want to report bug and error please contact Testing Technologies’ customer care department:

1.

Mr. Dirk Borowski

Phone:

Email: ttcn3-support@testingtech.com

+49 30 726 19 19 0

Requirements

1.1. Test Environment and Test Suite

TTworkbench is the TTCN-3 IDE and execution platform needed to run the test solution TTsuite-ITS. In case you are planning to develop your own test behavior (with TTsuite-ITS as a framework), TTworkbench Basic or Professional is required.

System Requirements

Operating Systems:

Microsoft Windows XP, Vista, 7 (x86-32, x86-64) Red Hat Enterprise Linux (GTK, x86-32, x86-64) Fedora (GTK, x86-32, x86-64) SUSE Linux (GTK, x86-32, x86-64)

Java:

Version JDK 1.6.*, 1.7.*, 1.8.* Download at www.oracle.com/technetwork/java/javase/downloads/index.html.

Please note that we strongly recommend using the above Java JDK. With the OpenJDK/IcedTea for Linux the TTworkbench license will not work correctly.

Memory:

2 GB (4 GB recommended)

1.2. Hardware Requirements

2 GB (4 GB recommended) 1.2. Hardware Requirements Communication via G5 Adaptation Box Communication via

Communication via G5 Adaptation Box

Hardware Requirements Communication via G5 Adaptation Box Communication via Ethernet Depending on your test

Communication via Ethernet

Depending on your test environment configuration, you will need a G5 adapter or connect directly to your SUT.

Cohda Wireless TM MK2 has been chosen as G5 adapter by ETSI.

In case you have some other version, please contact Cohda Wireless for the correct

application accordingly.

Cohda Wireless for the correct application accordingly. In case there is no SUT available, Cohda MK2

In case there is no SUT available, Cohda MK2 can be used as a simulated SUT too. An application running on

MK2 must be required from Cohda.

1.3. Software Requirements

1.3.1. Bridge Application

etsi.zip – provided by ETSI for G5 adapter

It contains the software running on the G5 adapter, including the bridge binary (for arm) and its startup script (rc.bridge). This script does some parameterization of the Cohda box; you may need to change some paths and probably the MAC filter parameters.

It includes the following three files:

Bridge

bridge application

bridge.conf

bridge configuration

rc.bridge

Ethernet configuration

1.3.2. Simulated SUT for MK2

A c2x-mk2-pkg file which simulates the ITS stack. You need to request this application from Cohda.

1.4. Official Document (tr_103099v010201p.pdf)

Please refer to ETSI TR 103 099 V1.2.1 (2014-05). Intelligent Transport Systems (ITS); Architecture of conformance validation framework

It includes test environment requirement, test adaptation development, upper tester message format.

2. Get TTworkbench and TTsuite-ITS

Reference ID and License File

Before you download TTworkbench and TTsuite-ITS, make sure you received a valid Reference ID and license file. Otherwise please contact our sales team at sales@testingtech.com.

Please use Testing Technologies’ download portal: www.testingtech.com/support/downloads.php.

Step 1

Select the latest version of TTworkbench (Express, Basic or Professional) for your platform.

Step 2

Enter your Download Reference ID (valid for TTworkbench).

Step 3

Download the file and save it in your favored directory.

NOTE! With the Linux version of Microsoft Internet Explorer, the browser saves the .jar file as .zip. Just rename it back to .jar.

Step 4

Use the link provided by our professional service team to download TTsuite-xxx (TTsuite_ITS_x.x.x.zip).

Step 5

Save the license file license.dat in your favored directory.

3.

Installation

3.1. TTworkbench

Step 1

Windows Platform:

Double click on TTworkbench-xxx-installer.exe (to be found on desktop or selected directory).

Linux Platform:

Use command line java-jar TTworkbench-xxx-installer.jar

Step 2

Follow the pop up installation wizard…

On request, browse for the valid license file license.dat, already saved in your favored directory.

(TTsuite-xxx and TTworkbench require a valid license file for execution, which was sent to you by mail.)

Step 3

Start TTworkbench from created desktop icon or menu entry.

Step 4

Start a new workspace by accepting the default workspace location on request or choose an existing one.

workspace location on request or choose an existing one. 3.2. TTsuite-ITS Step 5 In the TTworkbench
workspace location on request or choose an existing one. 3.2. TTsuite-ITS Step 5 In the TTworkbench
workspace location on request or choose an existing one. 3.2. TTsuite-ITS Step 5 In the TTworkbench
workspace location on request or choose an existing one. 3.2. TTsuite-ITS Step 5 In the TTworkbench
workspace location on request or choose an existing one. 3.2. TTsuite-ITS Step 5 In the TTworkbench

3.2. TTsuite-ITS

Step 5

In the TTworkbench menu, click on menu item Help Install New Software

Step 6

Click Add… Archive.

Choose the downloaded installation file TTsuite_ITS_x.x.x.zip. Click the check box with Test Suites Next Finish.

Accept the terms of license agreements. Finish and confirm to restart TTworkbench.

Step 7

After restart, please import the installed TTsuite-ITS.

Close the welcome tab. In the project view, just click on the right mouse button, go to menu:

File Import TTCN-3 TTCN-3 Test Solution Projects Select the installed Test Solution Projects Choose TTsuite-ITS Finish.

Solution Projects  Choose TTsuite-ITS  Finish . Further details about installation you can find in
Solution Projects  Choose TTsuite-ITS  Finish . Further details about installation you can find in

Further details about installation you can find in the integrated Users Guide. Click on:

Help Help Contents Testing Tech TTworkbench Users Guide.

4. Configure the Cohda Box as Bridge

Step 1

Unpack the etsi.zip file on your MK2 device into /mnt/ubi/etsi directory.

Step 2

Configure the parameters in bridge.conf and rc.bridge.

4.1.1. rc.bridge

This is the configuration used by the bridge application and contains a few parameters like channel number and Ethernet type.

The following 2nd rule of block “Setup the Radio-A AMS” needs to be changed.

# 2nd rule: match specific (mask defined) unicasters

# buffer all frames that have destination addresses

# deadbeefXXXX and ack them (if Ack was set in 802.11 Frame Ctrl Service bit)

# BABEBABE

fpga test write 0x200604 0xFFFFFFFF 0x00000000 0xefbeadde 0x00090000

Change to fpga test write 0x200604 0xFFFFFFFF 0x00000000 0xbebabeba 0x00090000

4.1.2.

bridge.conf

This is the configuration of the Ethernet setting.

# frequence mapping

channel=180

# Ethernet frame type

ether=0x0707

# execution mode. Used as bridge exec=bridge

# log file path

log_file=/mnt/ubi/etsi/bridge.log

4.1.3. bridge

This is the executable to be run in terminal. Three operations are available:

./rc.bridge start ./rc.bridge stop ./rc.bridge restart

5. Start the Bridge Application

The bridge application is located on Cohda Box under Linux.

Log in your Cohda Box (MK2 as example) over telnet or SSH (for example with PuTTY).

telnet <hostname/IPaddress of MK2>

Or start PuTTY, enter Hostname, choose SSH.

Start the bridge with root at /mnt/ubi/etsi

./rc.bridge start

the bridge with root at /mnt/ubi/etsi ./rc.bridge start 6. Start the Simulated SUT In case you

6. Start the Simulated SUT

In case you do not have an SUT, you can use a simulated one. Please request from Cohda if you need it.

Step 1

After you get the archive file, unpack it into the folder /mnt/ubi on the second Cohda MK2 (not on the same box where the bridge is running).

Step 2

In case you want to test GeoNetworking (GN), start SUT with root at /mnt/ubi ./c2x app mk2 release c ets gn.conf d fixes.conf

NOTE! If you are using the bridge configuration, change the parameter ITSG5Enabled in the ets-xxx.conf to 1.

For the other group test case, you need to replace the conf file name after -c. For instance, in case of CAM, just replace the option ets gn.conf with ets cam.conf .

7. Load Test Campaign

Step 1

Open the TTsuite-ITS folder in the Package Explorer (TTCN-3 Development Perspective).

Step 2

In the project root folder Open the folder double click on the test

campaign loader file xxx.clf (with the icon

(The perspective will automatically switch into the TTCN-3 Execution Management.)

).
).
tically switch into the TTCN-3 Execution Management.) ). Take ItsGeoNetworking_TestControl.clf as example, you will
tically switch into the TTCN-3 Execution Management.) ). Take ItsGeoNetworking_TestControl.clf as example, you will

Take ItsGeoNetworking_TestControl.clf as example, you will see the test cases listed as in the picture below.

you will see the test case s listed as in the picture below. First Steps User’s

8.

Configuration

Please configure your TTsuite-ITS according to the protocol and your local settings. You can use our MBS (Message Building System) to ease it up.

In the Parameter View of the Execution Management you find different parameters to change the settings for your individual test configuration.

Please click on the right mouse button over the parameter view or use the MBS button to open Message Building System.

view or use the MBS button to open Message Building System. You can access the single

You can access the single parameter and the attributes of single fields.

the single parameter and the attributes of single fields. When finished, just click on OK to

When finished, just click on OK to save the change. The changed parameters are called by the test system during runtime. You can run your test campaign with the new configuration at once without recompilation of your test cases.

For further details about Test Suite Properties, please refer to the integrated user’s guide.

Help Help Contents Testing Tech TTsuite-ITS.

9. Running Test Case

Execution:

Double click one test case or select one test case by single click and press the Execute tests button

case by single click and press the Execute tests button . Click on test campaign name

.

Click on test campaign name to edit the parameters in the Parameter View (below Management View).

For configuration details please refer to Chapter 8 Configuration.

Hint:

Parameters are configured with default value. Please use MBS (Message Building System) to change the value.

Further details please find under Help Help Contents Testing Tech TTsuite-ITS.

9.1. Analysis  Click on the TTCN-3 Graphical Logging tab. It shows the results of

9.1. Analysis

Click on the TTCN-3 Graphical Logging tab. It shows the results of the execution as a graphical output.

A single click on a “send” message arrow provides further details of the TTCN-3 template representation in the Test Data View. Double click on “send” and “receive” arrows for a coding in the Dump View.

A single click on a “match” or “mismatch” box shows you the received message compared to the expected TTCN-3 template. Mismatched values are marked red.

Management View

Result Analyser

values are marked red. Management View Result Analyser Test Parametrization 9.2. Saving Configurations and Test

Test Parametrization

9.2. Saving Configurations and Test Results

The current executed run of test cases can be saved in a *.tlz file by pressing the export button and selecting “Export Log” in the Management View.

The generated *.tlz file (with the icon

configuration (CLF) and the executed log traces.

the icon configuration (CLF) and the executed log traces. ) contains the current For reviewing, this

) contains the current

For reviewing, this file can be imported by pressing the import button and selecting “Import Log”.

To run configured test cases again, please press the import button and select “Import Log As New Session”.

In order to generate a test report, use this button.

Graphical Online Logging

a test report, use this button. Graphical Online Logging Further details about execution and savings you
a test report, use this button. Graphical Online Logging Further details about execution and savings you
a test report, use this button. Graphical Online Logging Further details about execution and savings you

Further details about execution and savings you can find in the integrated Users Guide, Chapter “Using TTworkbench TTman”. Click on: Help Help Contents Testing Tech TTworkbench Users Guide.

10. Details

10.1. Core Language Editor (CL Editor)

Each TTCN-3 file is view- and editable by double clicking in the CL Editor. As shown in Step 1 of “4. Running My First Test Case” you find the TTCN-3 source code (*.ttcn3) in folder ttcn3.

After opening the files, the source code will be syntactically checked and highlighted. In addition, an outline will be generated automatically and the go-to-declaration feature will be enabled.

TTCN-3 Compiler/ Validate Buttons

Outline

will be enabled. TTCN-3 Compiler/ Validate Buttons Outline P r o j e c t V

Project View

TTCN-3 Core Language Editor

10.2. TTthree (TTCN-3 Compiler)

For recompiling all TTCN-3 files, please open the main module (with the icon

click. Press the Rebuild button

NOTE! Compilation is only necessary if some test cases are changed or some new one is created. Otherwise, the generated *.jar files from TTCN-3 source are already available for execution.

from TTCN-3 source are already available for execution. ) in the CL Editor by double .

) in the CL Editor by double

available for execution. ) in the CL Editor by double . 10.3. TTman (Test Execution Management)

.

10.3. TTman (Test Execution Management)

In order to execute test cases and configure parameters, the CLF has to be loaded into the Test Execution Management.

In the project root folder, you will find several CLF files (with the icon

group according to the name, like ItsGeoNetworking_TestControl.clf for Geo Networking testing.

for Geo Networking testing. ). Please choose the clf for the testing Further details can

). Please choose the clf for the testing

Further details can be found in the integrated Users Guide, Chapters “Using TTworkbench CL Editor”, “Using TTworkbench TTthree” and “Using TTworkbench TTman”.

Click on Help Help Contents Testing Tech TTworkbench Users Guide.

11. Documents

Please refer ETSI TR 103 099 V1.2.1 (2014-05). Intelligent Transport Systems (ITS); Architecture of conformance validation framework

12. Appendix

12.1. Acronyms

ormance validation framework 12. Appendix 12.1. Acronyms CL Editor Core Language Editor MLF Module Loader

CL Editor

Core Language Editor

MLF

Module Loader File

CLF

Campaign Loader File

OS

Operating System

IUT

Implementation Under Test

SUT

System Under Test

MBS

Message Building System

TLZ

Test Logging Zip File

12.2. Notes

This document is subject to change without notice.

Testing Technologies IST GmbH Michaelkirchstraße 17/18 10179 Berlin, Germany

Phone

+49 30 726 19 19 -0

Fax:

+49 30 726 19 19 -20

Email:

info@testingtech.com

Internet:

www.testingtech.com

Testing Technologies, the Testing Tech logo, TTworkbench and TTsuite are trademarks or registered trademarks of
Testing Technologies, the Testing Tech logo, TTworkbench and TTsuite are trademarks or registered trademarks of
Testing Technologies IST GmbH. Other terms are used for identification purposes and are trademarks or registered
trademarks of their respective companies. Testing Technologies’ TTsuite is powered by Eclipse technology and
includes Eclipse plug-ins that can be installed and used with other Eclipse 3.7.2-based offerings. It includes software
developed by the Apache Software Foundation (http://www.apache.org/), ANTLR (http://www.antlr.org/), Tigris.org
(http://gef.tigris.org/), and L2FProd.com (http://L2FProd.com/).