vTESTstudio 2.0 SP2


Minimum required CANoe version for the usage of full functional range in vTESTstudio 2.0 SP2:

CANoe 8.5 SP3

Minimum required CANoe version for the usage of limited feature set in vTESTstudio 2.0 SP2:

CANoe 8.2 SP5

More details about vTESTstudio/CANoe version compatibility can be found on our Website.



  • Ethernet support: Ethernet functions are now available in CAPL und thus can be used in all test design editors.
  • Extended verdict concept supports the verdicts 'none', 'inconclusive' and 'error in test system' as well as 'passed' and 'failed'.
  • User Function Explorer gives an overview over all user-defined functions available in the current file.
  • Printing functionality now available for all kind of files (programming files, files from Test Table Editor and Test Diagram Editor, parameter files, stimulation curves).
  • Enumerations (in CAPL and C#) are supported as parameter type of interface functions.
  • Traceability matrix can be exported automatically with each test unit build.

Test Table Editor, Test Diagram Editor:

  • Usage of simple CAPL expressions in numeric input fields of test commands, e.g. „@mySysVar + 1“
  • The command [Await Value Match] now supports waiting for the next signal occurrence on the bus.

Test Table Editor:

  • Test case lists now supported for symbol parameters (signals, system variables, environment variables).
  • Definition of test case names in test cases lists possible by parameter value macros.
  • Test sequences can now be used within test fixtures.

Test Diagram Editor:

  • The graphical element [For Each] now supports iterating through struct lists defined in parameter files.

Waveform Editor:

  • Time unit for curve definition can be configured now.
  • Segments can be defined by the definition of durations instead of absolute times.

Execution (with CANoe 8.5 SP3):

  • Report file names can now be configured by the use of macros. For example, the current date and verdict can now be part of the file name.
  • Direct possibility to indicate the status and verdict of a test configuration within a set of system variables. Useful e.g. for usage within State Tracker Window.
  • Stop of test execution after each test tree element now possible, optionally after test tree elements with specific verdicts only.
  • New possibility to retrieve the current execution cycle number programmatically.
  • Additional report XSLT especially for cyclic executed test units.