AUTOSAR Test Suite Pack First Steps User s Guide

Transcription

1 AUTOSAR Test Suite Pack General Information This user s guide helps you to download and install TTworkbench, and leads you through configuring and running test cases of the AUTOSAR Conformance Test Suites. For a successful proceeding please follow the instructions step by step! If you need any assistance, please contact Spirent s customer care department: Mr. Dirk Borowski Manager Support Services Phone: support@spirent.com spirent.com

2 Table of Content 1. Requirements Test Environment and Test Suites Hardware Requirements 3 2. Get TTworkbench and AUTOSAR Installation TTworkbench AUTOSAR Test Suites Import AUTOSAR Test Suites Remote Server Configuration Load Test Campaign and Configuration Parameter View Running Test Cases Analysis Saving Configurations and Test Results Details Core Language Editor (CL Editor) TTthree (TTCN-3 Compiler) Capture File Related Documentation Appendix 15 spirent.com i

3 1. Requirements 1.1. Test Environment and Test Suites TTworkbench is the TTCN-3 execution platform needed to run the AUTOSAR Test Suites. System Requirements Operating Systems: Microsoft Windows 7/8/10 Linux (GTK2, x86-32, x86-64) Java 2 Platform: Memory: Version 8 JDK or JRE Download at We strongly recommend using the above Java JDK. With the OpenJDK / IcedTea for Linux the TTworkbench license will not work correctly! 2 GB (8 GB recommended) Software Requirement TTworkbench Test Package: Refer to the TTworkbench on C1/C50 First Steps User's Guide. Testability Protocol and Service Primitives AUTOSAR TC Release for full test automation: Implement on your own or use Spirent s Upper Tester Hardware Requirements Spirent C1 or C50 with BroadR-Reach. spirent.com 3/15

4 2. Get TTworkbench and AUTOSAR Test Suites Please use Spirent s Customer Service Center at Step 1 In case you are not registered yet, go to and fill in the registration form. The support team will check your data and notify you about your approval. Step 2 Login at Spirent s CSC and click on the download app tab on the left side. Step 3 Select the product line TTworkbench and filter for categories and operating system. Download the purchased TTworkbench version. Step 4 Select the release type Controlled Release, the Product Line TTworkbench and the Category TTsuites for TTworkbench. Download the AUTOSAR Test Suites file. 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 Browse for the valid license file license.dat already saved in your favored directory. (AUTOSAR Test Suites and TTworkbench require a valid license file for execution.) spirent.com 4/15

5 Step 3 Follow the pop up installation wizard and finish the installation. Step 4 Start TTworkbench from created desktop icon or menu entry. Step 5 Start a new workspace by accepting the default workspace location on request or choose an existing one AUTOSAR Test Suites Step 6 In the TTworkbench menu, click on menu item Help Install New Software... Step 7 Click Add Archive. Choose the downloaded installation file TTsuite-AUTOSAR- ReleaseBundle_xxx_archived-site.zip. Click Select All Next Next. Accept the terms of license agreements. Click Finish and confirm to restart TTworkbench. The AUTOSAR Conformance Test Suite Pack consists of the following protocol conformance test suites for Automotive Ethernet according to the AUTOSAR test specification running on Spirent C1 and C50 devices with BroadR-Reach network interface cards: TTsuite-AUTOSAR-IPv4 TTsuite-AUTOSAR-UDP TTsuite-AUTOSAR-TCP All test suites are prepared for full test automation via AUTOSAR Testability Protocol and Service Primitives (test stubs) and include frameworks for individual adaptation. You are able to customize test scenarios, for instance to modify or exclude test stub activities, or to add negative testing, etc. spirent.com 5/15

6 3.3. Import AUTOSAR Test Suites Step 8 Close the TTworkbench welcome tab. In the project view, click on the right mouse button, go to menu File Import TTCN-3 TTCN-3 Test Solution Projects Next. Step 9 Select the installed test solution projects and click on Finish. Included test suites: TTsuite-AUTOSAR-IPv4 TTsuite-AUTOSAR-UDP TTsuite-AUTOSAR-TCP Further details about installation you can find in the integrated User s Guide. Click on Help Help Contents Spirent TTworkbench User's Guide. spirent.com 6/15

7 4. Remote Server Configuration Step 1 TTworkbench enables the use of remote execution of the test suite on device connected to the same network of the Spirent C1/C50. In order to run the test suite remotely, the remote server has to be configured. In the TTworkbench main menu bar click on Window Preferences. Step 2 Navigate to TTCN-3 Execution TTman Engine. On the Engine tab click on Add Server, enter the IP address of the device (C50) in the Server Address field and select Use C1/C50 ports. Step 3 Select the configured TTman Server from the Server list. The Web Admin port enables you to access the server from a web interface for additional settings. After having set the parameters click on Check to see if the connection was established. The question mark should turn into a green check sign with a successful message. More information can be found in the TTworkbench on C1/C50 First Steps User's Guide. spirent.com 7/15

8 5. Load Test Campaign and Configuration Please configure your AUTOSAR Test Suites according to your local settings. You can use our MBS (Message Building System) to ease it up. For further details about Test Suite Parameters, please refer to the integrated user s guides. Click on Help Help Contents Using TTsuite-AUTOSAR-xxx. 5.1 Parameter View In the Parameter View of the Execution Management you find different parameters to change the settings for your individual test configuration. Step 1 Open the TTsuite-AUTOSAR-xxx folder in the Package Explorer (TTCN-3 Development Perspective). Here, TTsuite-AUTOSAR-UDP is used as an example. Step 2 In the clf folder, double click on the test campaign loader file Udp_Autosar_TestCases.clf (with the icon ). (The perspective will automatically switch into the TTCN-3 Execution Management). Udp_Autosar_TestCases.clf as example. spirent.com 8/15

9 The Parameters window enables you to configure the parameters specific to Device Under Test (DUT) as well as the Test System (TS). The module parameters allow a quick repetition of test cases with different values. All the parameters have a short description that explains their function. The configuration parameters in the DUT Parameters contain the hardware address and communication ports of the DUT and should be retrieved from it. The characteristic parameters are specific to some features that the DUT may or may not have, which will enable or disable some related test cases. Make sure to check the availability of these features on your device and set these parameters accordingly before you launch the test campaign. The Test System parameters require only the names of the interfaces that are used for the testing and their corresponding ports. The timers can also be customized to suit the user s needs. Please note the Parameters descriptions on the same view. For more configuration details please refer to the AUTOSAR Test Solutions integrated user s guides. Click on Help Help Contents Using TTsuite-AUTOSAR-xxx. You can click on the right button over the parameters view to use the Message Building System dialog. spirent.com 9/15

10 You can access the single parameter and the attributes of single fields in the dialog. 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. 5.2 Test Adapter Parameters View In addition, the Test Adapter Parameters window enables you to configure required Test Adapter parameters. Please note the TA Parameters descriptions on the same view. For more configuration details please refer to the AUTOSAR Test Solutions integrated user s guides. Click on Help Help Contents Using TTsuite-AUTOSAR-xxx. spirent.com 10/15

11 6. Running Test Cases Execution: Double click on one test case or select one test case by single click and press the Execute tests button ( ). Note: The Upper Tester application should be started before executing test cases. For more configuration details please refer to the AUTOSAR Test Solutions integrated user s guides. Click on Help Help Contents Using TTsuite-AUTOSAR-xxx. spirent.com 11/15

12 6.1. Analysis After execution, 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 or receive message arrow provides further details of the TTCN-3 template representation in the Test Data View, which you see the received message compared to the expected TTCN-3 template. Mismatched values are marked red. Double click on send or receive arrows for the raw messages in the Dump View. Management View Result Analyzer Test Parametrization Graphical Online Logging 6.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 ) contains the current configuration (CLF) and the executed log traces. spirent.com 12/15

13 For reviewing, this file can be imported by pressing the import button and selecting Import Log. In order to generate a test report, use this button. Further details about execution and savings you can find in the integrated Users Guide, Chapter Using TTworkbench TTman. Click on Help Help Contents Spirent TTworkbench User's Guide. 7. Details (for Development) 7.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 Project View TTCN-3 Core Language Editor spirent.com 13/15

14 7.2. TTthree (TTCN-3 Compiler) For recompiling all TTCN-3 files, please open the main module (with the icon double click. Press the Rebuild button. ) in the CL Editor by Please 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 Capture File To open the capture file (.pcap), double click on the INFO:PCAP or right click on it and open the file with an editor e.g. Wireshark ( spirent.com 14/15

15 8. Related Documentation To use Automotive AUTOSAR Test Solutions efficiently, you should be familiar with AUTOSAR Test Specifications, TTCN-3 and Spirent C1/C50. For additional resources refer to the following documentation: TTworkbench on C1/C50, First Steps User's Guide Automotive AUTOSAR Test Solutions integrated user s guides Help Help Contents Using TTsuite-AUTOSAR-xxx TTworkbench integrated User s Guide Help Help Contents Help Help Contents Spirent TTworkbench User's Guide T3Doc of AUTOSAR Test Solutions Help Help Contents Using TTsuite-AUTOSAR-xxx Chapter 5. T3Doc 9. Appendix Acronyms AUTOSAR CL Editor CLF MBS OS TLZ AUTomotive Open System ARchitecture Core Language Editor Campaign Loader File Message Building System Operating System Test Logging Zip File Notes This document is subject to change without notice. Spirent Communications, Michaelkirchstraße 17/18, Berlin, Germany Phone Fax: ttworkbench-sales@spirent.com Internet: spirent.com/automotive AMERICAS SPIRENT sales@spirent.com US Government & Defense info@spirentfederal.com spirentfederal.com EUROPE AND THE MIDDLE EAST +44 (0) emeainfo@spirent.com ASIA AND THE PACIFIC salesasia@spirent.com Spirent Communications, Inc. All of the company names and/or brand names and/or product names and/or logos referred to in this document, in particular the name Spirent and its logo device, are either registered trademarks or trademarks pending registration in accordance with relevant national laws. All rights reserved. Specifications subject to change without notice. Rev # 2017/04/06 15/15