AN001 - MTL - Configure MaTeLo To Generate Vector CANoe Test Cases PDF

APPLICATION NOTE
Configure MaTeLo to generate Vector CANoe test cases
Author
Anthony FAUCOGNEY
Abstract
This Application Note explains how to configure MaTeLo to generate CANoe test
cases, and automatically import them in the CANoe environment.
Keywords
MaTeLo, CANoe, CAPL, COM Automation, Test-cases generation.
Version
1.0 March 2012
Table
able of contents
1.
2.
3.
4.
5.
Overview ................................................................
................................................................
................................................................
................................
................................................................
.................................................
................................................. 3
1.1.
ALL4TEC MaTeLo Tool Chain ................................

................................................................
................................
................................................................
................................
.................................. 3
1.2.
Vector CANoe To
Tool
ol Chain ................................
................................................................
................................................................
......................................................................
...................................... 3
1.3.
Why integrate MaTeLo with CANoe? ................................................................

....................................................................................
.................................................... 3
1.4.
How integrate MaTeLo with CANoe? ................................................................

....................................................................................
.................................................... 4
Integration Concept ................................

................................................................
................................
................................................................
................................................................
................................................................ 5
2.1.
MaTeLo: Vector CANoe Test Automation Framework ................................

..........................................................
.......................... 5
2.2.
CANoe: Test case implementation with CAPL format ................................

...........................................................
........................... 5
2.3.
MaTeLo: Test Suite generation into the Vector CANoe CAPL format ................................
....................................
.... 7
2.4.
MaTeLo: Usage model configuration for CAPL ggeneration.

eneration. ................................
..................................................
.................. 7
2.5.
Test Script Generation................................................................

................................................................
................................................................
................................
...........................................
........... 8
Application Example................................
................................................................
................................
................................................................
..............................................................
.............................................................. 10
3.1.
Automotive Locking System ................................

................................................................
................................................................
................................................................ 10
3.2.
Functional requirements list ................................

................................................................
................................
...............................................................
............................... 11
3.3.
Automatic Test Framework ................................

................................................................
................................................................
................................................................
................................. 12
Project Deliveries ................................................................

................................................................................................
................................................................
................................................................
..................................
................................ 16
4.1.
MaTeLo usage model ................................................................

................................................................................................
................................................................
..........................................
.......... 16
4.2.
MaTeLo Requirements Library: ................................................................

................................................................
...........................................................
........................... 17
4.3.
MaTeLo Testor
Testor:: Test Cases and Automation Script files generation ............................... 17
4.4.
Automatic Test Case Import into CANoe ................................................................

................................................................
.............................................
............. 21
Conclusion ................................................................
................................................................
................................................................
................................................................
.............................................................................
............................................. 23
5.1.
Project deliveries ................................

................................................................
................................................................
.................................................
................. 23
................................................................
5.2.
Tool integration benefits ................................

................................................................
................................
................................................................
.....................................
..................................... 23
5.3.
Further Works ................................................................

................................................................
................................................................
.....................................................
..................................................... 23
5.4.
Contact ................................................................
................................................................
................................................................
................................................................
................................................................ 23
ALL4TEC
LAVAL (HQ) - MASSY - MUNICH
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
Table of Figures
Figure
Figure 1: MaTeLo Automatic Test Framework ................................................................
................................................................
..........................................................
.......................... 5
Figure 2: Vector CAPL Browser ................................
................................................................
................................................................
................................................................
.................................................
................. 6
Figure 3: MaTeLo ATF Test Scripting Configuration ................................................................
................................................................
..................................................
.................. 9
Figure 4: Vector CANoe Simulation Environment ................................................................
...................................................................................
................................................... 10
Figure 5: Test Operation Call Implementation (Stimulation) ................................................................
................................................................
.................................. 13
Figure 6: CAPL Browser with a stimulation test function implementation ................................
.............................................
............. 14
Figure 7: Test Operation C
Call
all Implementation (Verification) ................................................................
................................................................
.................................. 14
Figure 8: CAPL Browser with a test function implementation ................................................................
................................................................ 15
Figure 9: MaTeLo Usage Model for the Car Locking System ................................................................
...................................................................
................................... 16
Figure 10: Markov Chain Report ................................
................................................................
................................................................
................................................................
.............................................
............. 16
Figure 11: MaTeLo Requirements Library ................................
................................................................
................................
...............................................................
............................... 17
Figure 12: MaTeLo Testor GUI ................................
................................................................
................................................................
................................................................
................................................
................ 17
Figure 13: Test Suite Analysis with the Generation Report Windows .....................................................
..................................................... 18
Figure 14: Name of the saved test suite ................................
................................................................
................................................................
................................................................
................................. 18
Figure 15: Generated MaTeLo files ................................................................
................................................................
................................................................
................................
.........................................
......... 19
Figure 16: MaTeLo XML Test Cases ................................................................
................................................................
................................................................
................................
.........................................
......... 19
Figure 17: MaTeLo Requirements Coverage Analysis Report ................................................................
................................................................
................................. 20
Figure 18: Partial CAPL Test Case Implementation ................................................................
................................................................
.................................................
................. 20
Figure 19: Partial CAPL Test Suite Implementation ................................................................
................................................................
.................................................
................. 21
Figure 20: CANoe Automation Script ................................
................................................................
................................
................................................................
......................................
...................................... 21
Figure 21: Automatic Creation of the Final CAPL file ................................................................
................................................................
..............................................
.............. 21
Figure 22: Added Test Cases into the CANoe Test Environment ................................
............................. 22
.............................................................
Figure 23: CANoe XML Report
Report................................
................................
................................................................
................................................................
.................................................
................. 22
................................................................
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
1. Overview
This application n
note
ote aims to explain how to use ALL4TEC MaTeLo instead of generating test cases for
Vector CANoe.
1.1. ALL4TEC MaTeLo Tool Chain
MaTeLo is a tool chain developed by ALL4TEC (www.all4tec.net
www.all4tec.net
www.all4tec.net) that implements the Model Based
Testing approach. In a user friendly environment
environment,, MaTeLo offers an integrated set of components and
features to enable test engineers in design
designing
ing their tests
test based on usage models
models..
Then, th
the
e test cases are automatically generated
enerated from the model depending on the user selected test
strategy.
The tool is mainly used in automotive at the product and system validation level.
In general, MaTeLo manages successfully test projects in the fields of automoti
automotive,
ve, railway or energy by
providing professional and valuable features to obtain a better test coverage and a higher engineering
productivity.
1.2. Vector CANoe Tool Chain
CANoe is a tool developed by Vector Informatik ((www.vector
www.vector-inform
www.vector informatik.com
informatik.com)
atik.com that offers simulation,
analysis and test
ing feature
features for distributed embedded networks development.
development. Thanks to its support
testing
of many busses, protocols and networks, CANoe is a very flexible solution for automotive system
systems
development and validation. With its capability to handle a partly real, partly simulated network, the
so called CANoe Test Feature Set enables to define and execute test
tests that address the system under
development.
The tool is a de facto industry standard for distributed system
systemss analysis and testing in automotive. It is
sometime the only comfortable way to interact with ECUs.
1.3. Why integrate MaTeLo with CANoe?
As soon as finding error
errors at early stage of the development cycle bring a high cost reduction,
reduction, the
interest to use MaTeLo for generating test cases during the network and system simulation make
makes
sense.
That is the reason why
why,, as soon as the system development start
starts,, tests
test can be designed, and
generated with MaTeLo
MaTeLo.. Then, as soon as the system can be simulated, the MaTeLo test cases will be
executed on the CANoe environment to insure high test coverage at low cost.
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
1.4. How integrate MaTeLo with CANoe?

Both solutions are very open and accept many approaches
approaches:
CANoe accepts its test cases definition with CAPL language

language,, .NET
.NET,, COM server, XML, CSV, and
text formats for describing test cases.
text
MaTeLo allows ttest
est cases generation into XML, sscript
cript and text
ext formats,
formats, NI TestStand or EXA
EXAM..
Because CAPL ((the

the CANoe c-like
like language meaning Communication
Communication Access Programmin
Programming Language
Language)
is the most integrated and offer
offerss the most test capabilit
capabilities,, this approach has been chosen and will be
explained in this application note
note.
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
2. Integration Concept
2.1. MaTeLo
MaTeLo:: Vector CANoe Test Automation Framework
MaTeLo doesnt support in a fully integrat
integration
ion the Vector CANoe Test Automation Framework
Framework. First
First,, it
will be necessary to define a proprietary MaTeLo
Automatic
Automatic Test Framework aas knows
knows as ATF as the
following:
Figure 1: MaTeLo Automatic Test Framework
We can see different test operations, aka TO, that represent capable test services
service which can be
handle by the MaTeLo ATF, so
o for this paper Vector CANoe.
By convention, the TO starting by Admin_
Admin_ are used to deal with the construction
construction of the test script
structure and its automatic insertion in the end test tool.
2.2. CANoe: Test case implementation with CAPL format
The MaTeLo output format for test case generation will be CAPL (*.can).
(*.can). This CAPL file (categorized in
CANoe as CAP
CAPLL Test Node ) will host the test cases definition and its implementations as well as the
test functions libraries implementation. The CAPL structure is the following:
TestControl
o MainTest()
Testcase
testfunction
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
Figure 2:: Vector CAPL Browser
In the CAPL browser above, the

he MainTest()
MainTest folder can be understood as the main loop as test
program . It in
cludes all test variables and functions declaration, as well as the main program loop
includes
that is called by the CANoe runtime environ
environment.
nvironment. Then the main call is scheduling all the CAPL test
cases defined in the CAPL file.
The
test
estcase
ase
definitions and the implementation of the CAPL test cases by calling
folder owns the definitions
and configuring CAPL test functions to implement a functional test sequence with its optional flow
controls.
The
test
estfunction
unction folder owns the defin
definition
ition and implementation of the CAPL test function
functionss,, which
each implement an atomic functional action (stimulation, verification or general operation
operations)). Those
functions will be used to get access to the System
System under Test aka SUT
SUT. The CAPL test functions can
use all the CANoe capabilities to perform an action. It means that added to the easy access function of
the SUT, complexes stimulations
stimulations or verifications
verifications can be implemente
implemented
d in such functions.
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
2.3. MaTeLo: Test Suite ggeneration

eneration into the Vector CANoe CAPL format
MaTeLo is performing the following generated test suites:
Test Suite
o Test Case 1
o Test Case 2
Test Step 1
Test Step 2
Stimulation
o Test Operation 1
o Test Operation n
Verification 1
o Test Operation 1
o Test Operation n
Verification n

Test Step n
o
o Test Case n
In the MaTeLo language,
A Test
Test Suite
Suite means a test generation shoot
A Test
Test Case
Case means a selected path of the MaTeLo usage model
A Test
Test Step
Step means a transition in the usage model
2.4. MaTeLo: Usage model configuration for CAPL ggeneration.

eneration.
Thanks
hanks to the so called MaTeLo e
encapsulation
ncapsulation features, it enables
enabl to define global association of
Test Operations with the usage m
model
odel items classes ((Test
Test Suite,
Suite, Test Case
Case,, Macro Chain and
Transition)
Transition).. The configuration can be easily and efficiently done to generate the expected outcome.
2.4.1. Test Suite
uite level
evel (test generation sshoot)
hoot)
Based on the CAPL file structure, every test suite must contain the following informat
information:
ion:
Header
o File Header
o Main Test
o Test Suite Description
o Test Strategy Description
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net

Footer
o Test Case Folder Declaration
o Test Functions Implementation
o File Footer
2.4.2. Test Case level (usage m
model
odel path)
ath)
Header
o Test Case Call
o Test Case Description
o Test Case Covered Requirement
o Test Case Declaration
Footer
2.4.3. Test Step level (ttransition)
ransition)
Header
o Test Step Description
o Test Step Covered Requirements
o Test Functions Calls with valued parameters
Footer
2.4.4. Generation Workflow
Because the script generation is done on the fly, we can easily understan
understand that this structure cannot
be generated in one single shoot. That is the reason why the generation process has been split into 2
generation actions + 1 automation action.
The process will generate 3 files from MaTeLo:
2 parti
partials
als files (CAPL *.can) for Test Suite and Test Case implementations
mplementations
o One file for the test case implementation (test functions calls)
o One file for the test suite implementation (test cases calls)
1 file (Visual Basic Script *.vbs) for CANoe Automation in order to add the generated test
cases automatically.
2.5. Test Script Generation

The following Test Script configuration can be adopted in MaTeLo
MaTeLo::
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
Figure 3:: MaTeLo ATF Test Scripting Configuration
Because the generation is done on the fly, the Test

Test Suite
Suite file
file must be generated before the
the
Test Cases
Cases file.
file.
Then the CANoe automation file will concatenate the 2 partial CAPL files into the final CAPL
file. Then, via the CANoe COM server,
file.
server, it will sta
start
rt remotely and automatically CANoe in order
to add the generated test suite into the CANoe Test Environment.
Environment
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
10
3. Application Example
Aiming to show this concept on a concrete project, a selected CANoe project, delivered as demo in the
release,
release is used to demonstrate the interoperability.
3.1. Automotive Locking System
Figure 4:: Vector CANoe Simulation Environment
In this Application Node, only a part of the system will be taken into account.
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
11
3.1.1. Inputs / Outputs definition

efinition
Type
Panel Label
Symbol Type
Symbol Name
N ame
Available Value
Push Button
Input
Open Car
CAN signal
LockRequest
[idle ; 2]
Push Button
Input
Close Car
CAN signal
LockRequest
[idle ; 2]
Button
Input
Engine
CAN signal
EngineRunning
[0 ; 1]
Push Button
Input
Speed Up
EnvAccelerate
[0 ; 1]
Push Button
Input
Slow Down
EnvDecelerate
[0 ; 1]
Tail tell
Output
Lock State
CAN signal
LockState
[Locked ;
Unlocked]
Gauge
Output
Velocity
CAN signal
Velocity
[--100,350]
100,350]
Environmental
Variable
Environmental
Variable
3.2. Functional requirements

requirements list
ist
Requirement Name
Automatic_Locking
Lock_Action
Lock_Action
Unlock_Action
ALL4TEC
Phone: +33(0)2 43 49 75 30
Description
Involved Input
Involved Output
WHEN
The car is running
IF
The speed of the car
reach 50 km/h
THEN
The car become locked
IF
The button lock is
pressed
THEN
The car become locked
IF
The button lock is
pressed
THEN
The car become
unlocked
unlocked
Velocity
LockState
LockRequest
LockState
LockRequest
LockState
V1 March
March 2012
www.all4tec.net
12
3.3. Automati
Automaticc Test Framework
The following test operation
operations are required to performed the test case automation of the defined
requirements.
requirement .
3.3.1. Stimulation operations:
operations
Name
Push_Lock
Description
Change the signal lockrequest
to 1 , send the CAN frame, wait
that the CAN frame has been
confirmed on the CAN bus, and
then release the lockrequest
signal to 0, and confirm that the
CAN frame appear on the bus
Push_Unlock
Change the signal lockrequest

None
None
to 2 , send the CAN frame, wait
that the CAN frame has been
confirmed on the CAN bus, and
then release the lockrequest
signal to 0, and confirm that the
CAN frame appear on the bus
Set the EngineRunning to 1
None
and wait for its apparition on the
bus.
Set the EngineRunning to 0
None
None
and wait for its apparition on the
bus.
If the car_speed is lower than the Expected_Car_Speed
expect car speed, then accelerate.
[0,330]
If the car_speed is higher than
expect car speed, then decelerate
Start_Engine
Stop_Engine
Set_Car_Speed
ALL4TEC
Phone: +33(0)2 43 49 75 30
Parameters
None
None
Inputs/Outputs
Inputs/Outputs Involves
Input :
LockRequest
Input :
LockRequest
Input :
EngineRunning
Input :
EngineRunning
Input :
EnvAccelerate
EnvDecelerate
Output :
Velocity
V1 March
March 2012
www.all4tec.net
13
An example of stimulation test operation call:
Figure 5:: Test Operation Call Implementation (Stimulation)
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
14
The implementation of this test function is done by the following:
Figure 6:: CAPL Browser with a stimulation test function implementation
3.3.2. Verification Test Operations:

Name
Check_CarIslocked
Check_Carisunlocked
Description
Verify that the Lockstate
signal is 1
Verify that the Lockstate
signal is 0
Parameters
none
none
Inputs/Outputs In
Involves
volves
Output :
Lockstate
Output :
Lockstate
An example of verification test operation:
Figure 7:: Test Operation Call Implementation (Verification)
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
15
The implementation of this test function is done by the following:
Figure 8:
8 CAPL Browser with a test function implementation
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
16
4. Project Deliveries
The full project can be found on our website at the following web address:
address: www.all4tec.net
4.1. MaTeLo usage model
To keep a simple understandable example
example,, the model is only about a single layer:
Figure 9:: MaTe

MaTeLo
Lo Usage Model for the Car Locking System
The usage model has been designed with MaTeLo Usage Model Editor. Even if only 3 requirements
explain the system needs, almost 20 transitions are necessary to cover the required use cases.
Figure 10:
10: Markov Chain Report
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
17
4.2. MaTeLo Requirements Library:

MaTeLo project rrequirements
equirements definition and associations
associations:
Figure 11:
11: MaTeLo Require
Requirements
ments Library
4.3. MaTeLo Testor: Test Case

Casess and Automation Script files generation
Following full requirements coverage, the Arc Coverage generation algorithm has been chose to
generate the expected test cases:
Figure 12:: MaTeLo Testor GUI
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
18
After the generation, this windows report

reportss about th
the
e potential coverage of the created test cases.
Because of the Arc Coverage algorithm, we confirm that 100% of states & transitions have been
covered by the test cases. Following the methodology guide line, only transitions are used to design
the test of requirements. So 100% of the requirements are covered by the test case.
Figure 13:
13: Test Suite Analysis with the Generation Report Windows
The Arc Coverage algorithm just request 24 step to fully cover the whole model.
Figure 14:
14: Name of the saved test suite
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
19
The generated files have been automatically generated by MaTeLo:
Figure 15:
15: Generated MaTeLo files
The ggenerated
enerated MaTeLo test cases can be reviewed and analyzed with
with a style sheet that renders the
MaTeLo XML Test Suite as the following:
Figure 16:
16: MaTeLo XML Test Cases
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
20
A traceability table is generated to trace requirements with test cases and model items:
Figure 17:: MaTeLo Requirements Coverage Analysis Report
Then 2 partials CAPL files and 1 Visual Basic Script has been generated:
Figure 18:
18: Partial CAPL Test Case Implementation
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
21
Figure 19:
19: Partial CAPL Test SSuite
uite Implementation
Figure 20:: CANoe Automation Script
4.4. Automatic Test Case Import into CANoe

After the execution of the V
Visual
isual Basic SScript,
cript, the final CAPL file is automatically created:
Figure 21:: Automatic Creation of the Final CAPL file
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
22
The
he script
script control
controls CANoe
CANoe, via its COM server
server, and add
adds the MaTeLo generated test case into the
CANoe Test Environment.
Figure 22:
22: Added Test Cases into the CANoe Test Environment
Then,
Then, after executing the test case, the following report is automatically created:
Figure 23:: CANoe XML Report
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net
23
5. Conclusion
5.1. Project deliveries
Through this case study and their explanations, we notice that MaTeLo and CANoe are able to
integrate together. Thanks to this integration, a continuous process can be handled.
Thanks to MaTeLo, CANoe users are benefiting from a high
high-end
end Model
Model-Based
Based Testing approach to
build their test cases.
5.2. Tool integration benefits
The combinati
combination
on of the 2 tools will help to achieve a very productive engineering works.
MaTeLo help in making a good validation campaign, focus on requirements use case testing,
independently of the system implementation.
MaTeLo can use all the CANoe features (thanks to CAPL) and test patrimonies to run the campaign as
earliest as possible and during the whole development cycle.
5.3. Further Works
Additional integration can be handled to quickly extend this MaTeLo project and then enable users to:
- Get
CANoe
oe CAPL test function into the MaTeLo environment
et automatically the CAN
- Forward
orward CANoe test case
cases verdict to MaTeLo TCA
- Add
dd more MaTeLo usage model description & covered requirement
requirements into the CAPL test
cases
5.4. Contact
If you need more information or need more on this context, feel free to contact ALL4TEC at:
ALL4TEC
Contact
E-mail
mail
Phone
France Office
Pierre
MARTINETTI
pierre.martinetti@all4tec.net
+33(0)6
+33(0)6 08 21 12 03
Germany Office
Gabor
MATYUS
gabor.matyus@all4tec.net
+49(0)
+49(0) 17 28 971 101
Business Development
Anthony
FAUCOGNEY
anthony.faucogney@all4tec.net
+33(0)2 43 497 532
fae@all4tec.net
+33(0)1 80 750 755
Technical support
ALL4TEC
Phone: +33(0)2 43 49 75 30
V1 March
March 2012
www.all4tec.net

AN001 - MTL - Configure MaTeLo To Generate Vector CANoe Test Cases PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AN001 - MTL - Configure MaTeLo To Generate Vector CANoe Test Cases PDF

Uploaded by

Copyright:

Available Formats

APPLICATION NOTE

Configure MaTeLo to generate Vector CANoe test cases

MaTeLo, CANoe, CAPL, COM Automation, Test-cases generation.

1.0 March 2012

Configure MaTeLo to generate Vector CANoe test cases

ALL4TEC MaTeLo Tool Chain ................................

Why integrate MaTeLo with CANoe? ................................................................

How integrate MaTeLo with CANoe? ................................................................

Integration Concept ................................

MaTeLo: Vector CANoe Test Automation Framework ................................

CANoe: Test case implementation with CAPL format ................................

MaTeLo: Usage model configuration for CAPL ggeneration.

Test Script Generation................................................................

Automotive Locking System ................................

Functional requirements list ................................

Automatic Test Framework ................................

Project Deliveries ................................................................

MaTeLo usage model ................................................................

MaTeLo Requirements Library: ................................................................

Automatic Test Case Import into CANoe ................................................................

Project deliveries ................................

Tool integration benefits ................................

Further Works ................................................................

Configure MaTeLo to generate Vector CANoe test cases

Configure MaTeLo to generate Vector CANoe test cases

Configure MaTeLo to generate Vector CANoe test cases

1.4. How integrate MaTeLo with CANoe?

CANoe accepts its test cases definition with CAPL language

Because CAPL ((the

Configure MaTeLo to generate Vector CANoe test cases

Figure 1: MaTeLo Automatic Test Framework

Configure MaTeLo to generate Vector CANoe test cases

Figure 2:: Vector CAPL Browser

In the CAPL browser above, the

Configure MaTeLo to generate Vector CANoe test cases

2.3. MaTeLo: Test Suite ggeneration

In the MaTeLo language,

2.4. MaTeLo: Usage model configuration for CAPL ggeneration.

Configure MaTeLo to generate Vector CANoe test cases

2.5. Test Script Generation

Configure MaTeLo to generate Vector CANoe test cases

Figure 3:: MaTeLo ATF Test Scripting Configuration

Because the generation is done on the fly, the Test

Configure MaTeLo to generate Vector CANoe test cases

Figure 4:: Vector CANoe Simulation Environment

Configure MaTeLo to generate Vector CANoe test cases

3.1.1. Inputs / Outputs definition

3.2. Functional requirements

Configure MaTeLo to generate Vector CANoe test cases

Change the signal lockrequest

Configure MaTeLo to generate Vector CANoe test cases

An example of stimulation test operation call:

Figure 5:: Test Operation Call Implementation (Stimulation)

Configure MaTeLo to generate Vector CANoe test cases

The implementation of this test function is done by the following:

Figure 6:: CAPL Browser with a stimulation test function implementation

3.3.2. Verification Test Operations:

An example of verification test operation:

Figure 7:: Test Operation Call Implementation (Verification)

Configure MaTeLo to generate Vector CANoe test cases

The implementation of this test function is done by the following:

Configure MaTeLo to generate Vector CANoe test cases