winIDEA HelpVector CANoe
The isystem.connect interface allows driving iSYSTEM BlueBoxes from almost any external application being used in the development labs. These external applications are typically test environments controlling the target microcontroller and acquiring specific data (memory content, register values, trace, profiler, code coverage) from the target microcontroller.
This document describes how to remotely drive iSYSTEM BlueBox from Vector CANoe Test Automation Module. As an alternative, the vTESTstudio integration is described as well.
.NET for C# test automation scenario is described.
Prerequisites
•Vector CANoe
•Vector vTESTstudio (optionally for test units)
•winIDEA
|
It is recommended to use multi-threading. CANOe is using only one single thread for simulation and testing. That means while waitUntilStop function runs, nothing in CANoe runs (e.g. event fetching from the drivers, CAPL processing, etc.) which can cause delays >1ms. |
winIDEA SDK in Test Environment
CANoe setup
 1. Run under View / Test setup / Test Environments for Test Modules |
||
 2. Right-click on Test Setup and select New Test Environment
|
||
 3. Rename the test environment and save it to disk |
||
 4. Right click the test environment and select Insert .NET test module |
||
 5. Right click the test environment and select Configuration |
||
 6.. Under Common tab rename the .NET Test Module and select the test script file (extension .cs for C#). |
||
 7. Under Components tab register the iSYSTEM .NET library (IConnectCSLib.dll). This library is valid for C# .NET scripts and could be downloaded from iSYSTEM home page isystem.connect SDKs.
|
||
 8. Edit and prepare .cs script.
Refer to a downloadable Canoe configuration package iSYSTEM.Connect.Canoe.TestModulesExample.zip “iSystem.Connect.NET advanced CS sample” (file name testModules\AdvancedExample.cs), could be a good starting point for the script implementation. |
||
 9. Run the simulation and test. |
||
 Test results are visible in the Write Window. |
winIDEA SDK and vTESTstudio
In vTESTstudio, you can implement tests with the help of CAPL and C# files as well as in tabular and graphic forms. In so doing, the different test languages can be easily combined. The executable entity programmed in vTESTstudio is called a test unit. It comprises all files required for the test. A test unit created in vTESTstudio has the file extension *.VTUEXE. This can be configured and executed in CANoe.
vTESTstudio setup
 1. Create a new vTESTstudio project |
 2. Create a new test unit |
 3. Add a C# file to the test unit |
 |
 4. Copy the .NET assembly iConnectCSLib.dll either to the vTESTstudio test unit folder next to the C# file or to one of its libraries. |
 5. Add the .NET assembly iConnectCSLib.dll to the test unit. Now the the functionality of the iConnectCSLib.dll is available within the C# file. |
 6. Define test cases, test functions or functions within the C# file accessing the API of the iConnectCSLib.dll. Use the attribute [Export] to be able to call these functions in other test design languages as well, e.g. in the Test Table Editor. |
 7. Use the C# methods to define your test sequence - either in C# editor or in the Test Table Editor or in the Test Diagram Editor. |
 8.Build the executable test unit *.VTUEXE. |
|
Vector CANoe with vTESTstudio integration sample is provided in the compressed archive iSYSTEM.Connect.Canoe.Example.Testunit.zip |
