One common language for domain experts and test engineers

Size: px

Start display at page:

Download "One common language for domain experts and test engineers"

Jesse Jackson
10 years ago
Views:

1 One common language for domain experts and test engineers Cost-effective creation and reuse of test sequences with Vector s Test Automation Editor V

2 Agenda > Overview Introduction to the Test Automation Editor Example Summary Slide: 2

Overview Setup for Testing Test Automation Editor Test-Environment failed passed Test Report Create test sequence Control and execute test Uses many ASAM standards CANoe HIL Test System Test Engineer

3 Overview Setup for Testing Test Automation Editor Test-Environment failed passed Test Report Create test sequence Control and execute test Uses many ASAM standards CANoe HIL Test System Test Engineer Test Spec. GPIB, RS232, UDP, TCP, DAQ, IOcab,... CANcardXL, VN2600 Able to understand Profound Knowledge Measurement & Test Hardware: e.g. Vector VT System, Digital/Analog I/O System under Test (SUT) Bus Interfaces Domain Expert Network (CAN, LIN, MOST, FlexRay, DoIP, K-Line) Slide: 3

4 Agenda Overview > Introduction to the Test Automation Editor Example Summary Slide: 4

5 Introduction to the Test Automation Editor Creation and maintenance of CANoe Test Modules Test sequence based on pre-defined test functions of CANoe Programmed User-Library test functions and test cases directly accessible per drag & drop Environment data (like signals, sensor data, ) are available and can be accessed conveniently author is guided very well and can focus on the real task: creation of a test Slide: 5

directly accessible per drag & drop Environment data (like signals, sensor data, ) are available and can

6 Agenda Overview Introduction to the Test Automation Editor > Example Summary Slide: 6

7 Example Test Requirement Example: Simulated central locking system in CANoe Test Requirement: Crash during the engine is running and velocity is 60 km/h has to open the locked central locking system Condition 1 (Test Preparation): Set system to initial state (Start engine and accelerate to 60 km/h) Condition 2 (Main Condition): Crash applies and within 200 ms the central locking system is unlocked Condition 3: Reset system to initial state Slide: 7

Preparation): Set system to initial state (Start engine and accelerate to 60 km/h) Condition 2 (Main Condition):

Example Test Implementation: Condition 1 Condition 1: Before the main test set the system to initial state (Start engine and accelerate to 60 km/h) Insert into the Preparation section

8 Example Test Implementation: Condition 1 Condition 1: Before the main test set the system to initial state (Start engine and accelerate to 60 km/h) Insert into the Preparation section > a Initialize-primitive and parameterize it (start engine) > the CAPL test function TF_AccelerateDecelerate and set parameter targetspeed to 60 (raise velocity up to 60 km/h) Slide: 8

section > a Initialize-primitive and parameterize it (start engine) > the CAPL test

9 Example Test Implementation: Condition 2 Condition 2: Stimulate crash sensor value, verify that within 200 ms the central locking system is unlocked Insert a StateChange-pattern into the Main Sequence and parameterize it Slide: 9

the central locking system is unlocked Insert a

10 Example Test Implementation: Condition 3 Condition 3: Reset the system to initial state Insert a Initialize-primitive into the Completion section and parameterize it Slide: 10

11 Agenda Overview Introduction to the Test Automation Editor Example > Summary Slide: 11

12 Summary Focus on test task: check functionality of SUT No implementation stuff Review of test parameters possible also by domain expert Cost-effective creation and maintenance of test sequences: Easily utilize build-in test functions of CANoe Open for user extensions: > Custom test functions can be implemented in CAPL and.net and used / parameterized in Test Automation Editor Reuse of user-implemented libraries Same tool can be used by different teams that specify tests for the different development phases (like system and acceptance tests) Full access to domain symbols like bus signals, value enumerations, hardware signals High usability Slide: 12

net and used / parameterized in Test Automation Editor Reuse of user-implemented libraries Same tool can be used by different teams that specify tests for the

13 Thank you for your attention. For detailed information about Vector and our products please have a look at: Hall 1, Booth Author: Siegfried Beeh, Friederike Gengenbach Vector Informatik GmbH Ingersheimer Str Stuttgart Slide: 13

have a look at: Hall 1, Booth 1830 www.vector.

Laboratory Course Industrial Automation. Experiment Nr. 6. Introduction to the FlexRay bus system. Brief User Guide IAS Demonstrator Go-Cart

Universität Stuttgart Institut für Automatisierungs- und Softwaretechnik Prof. Dr.-Ing. M. Weyrich Laboratory Course Industrial Automation Experiment Nr. 6 Introduction to the FlexRay bus system Brief