vTESTstudio is a powerful development environment for creating automated ECU tests. In order to increase the efficiency in terms of test design and to simplify the reusability it provides either

programming-based,

table-based and

graphical test notations and test development methods.

vTESTstudio can be employed in all product development phases: from model testing right through to system validation. Thanks to the use of open interfaces vTESTstudio can be simply incorporated into existing tool landscapes.

Advantages

Broad range of applications through the use of various test design editors

Flexible parameterization of test sequences with scalar values, test vectors and stimulation curves which can be accessed from all test design languages

Universal variant support for structure, implementation and parameterization of tests

Simple maintenance of test projects on account of the modular structure and a variety of structuring options such as libraries and folders

Test Table Editor

Test Table Editor

You can use the Test Table Editor to define linear test sequences in an easy way in table format without requiring any programming knowledge.

The editor provides you with special commands for stimulating and testing the “System Under Test”. It lets you conveniently parameterize the commands by drag & drop from explorers and offers intelligent input assistance.

Show more

Test Sequence Diagram Editor

Test Sequence Diagram Editor

The Test Sequence Diagram Editor is available with the vTESTstudio Option "Graphical Test Design".

This Editor lets you create tests in graphic form. vTESTstudio automatically generates a test case for each path in the diagram. The easy-to-understand graphic representation gives you an easy way to review even complex test logic.

Test code in table-based notation can be assigned to each graphic element. For this test code the same commands are available as in the Test Table Editor.

Show more

State Diagram Editor

State Diagram Editor

The State Diagram Editor is available with the vTESTstudio Option “Graphical Test Design”.

With the State Diagram Editor you model the expected behavior of the SUT as state transition diagram. vTESTstudio automatically generates test cases out of this test model. For the test case generation you can choose between several algorithms as Chinese Postman and breadth search.

Test code in table-based notation can be assigned to each graphic element. For this test code the same commands are available as in the Test Table Editor.

Show more

Programming Editor

CAPL Editor

The two programming editors, one for C# and one for CAPL, provide you with the functions of a modern development environment. Its features – which include automatic text completion, syntax highlighting and error recognition – simplify your work even while typing.

You can define sequential test flows or event-based test flows in both programming languages – CAPL and C#. Event-based test flows are enabled by special language elements that can be used to react to events of the test environment, e.g. to preprocess signals.

To implement tests in C# you can also use Microsoft Visual Studio. A dedicated integration with vTESTstudio is available.

Show more

Parameters & Waveforms

Parameter Editor

Parameter Editor

You can attain a higher level of reuse of functions, test cases and parameters, if you define and manage ECU parameters and test vectors in separate files. vTESTstudio lets you access the parameters for a test sequence from all implementation languages.

Parameters and test vectors can be defined as scalars and as a list. These lists make it very convenient for you to perform iterations of the test sequences, e.g. if you wish to execute different variants of a test vector with the system under test.

A convenient editor is available to you in vTESTstudio for editing the parameter files. However, it is also possible to edit the files in an external editor, e.g. in Microsoft Excel, by saving the files in a simple csv format.

Show more

Waveform Editor

Waveform Editor

By the use of the so-called Waveform Editor curves for the stimulation of the system under test can be defined. Predefined segment types (sinus, pulse …) support you in defining e.g. voltage curves by ECU test standards like LV124. Multiple curves can be synchronized easily within the same editor.

Additionally to stimulating curves it’s possible to define check points directly in the graphical user interface. This enables you to validate expected behavior of the system under test synchronized with the stimulated values.

Show more

Classification Tree Editor

Classification Tree Editor

To find test case data is supported by the so-called classification tree editor. The definitions of classifications and equivalence classes in a graphical interface supports you in fast, convenient finding of the number of test vectors needed.

The explicit support of boundary values additionally helps you in considering critical values as minimum and maximum values of equivalence classes.

Show more

Variant Handling

vTESTstudio offers you full support of ECU variants and test variants. In vTESTstudio, variants are represented by so called variant properties. Within a test project, you define as many variant properties as you wish, e.g. the ECU variant “Country [US, Europe]” or the test variant “Coverage [Full, Regression]”.

Define the value of a variant property in advance when designing the test, or set it shortly before the test starts. You can define both the test structure and the test sequence and parameter values dependent on variants. Your benefit is the increased reuse of test functions, parameters and entire libraries, even across different product lines.

Variant-depending Test Execution Tree

The structure of the test execution tree can depend on one or more variant properties. For example, individual test cases can only be relevant for a specific instance of an ECU, or entire test groups can only be executed in a specific test variant (for example, a complete test in contrast to a regression test).

Variant conditions for test cases and test groups can be based on one or more variant properties. Multiple conditions can be linked using logical operators.

If the condition defined for a test case or a test group is not fulfilled, this element does not appear for the test execution in CANoe.

Show more

Variant-depending Test Sequence

The execution sequence within a test case can depend on one or more variant properties. This can be modeled using corresponding If-/Else statements or special graphical elements.

Show more

Variant-depending Parameters

If individual values (e.g. configuration parameters for the ECU) depend on a variant property, this can be defined in the parameter editor. You can also define variant-dependent list parameters. For example, the set of values in a list of to be tested temperatures may depend on the variant property "Test depth": more temperature values are tested for a complete test than for a smoke test.

At test execution time, the appropriate values for the set variant are automatically used without having to adjust the actual test sequence (e.g., in the test table test chart editor).

Show more

Test Coverage

Test Case Lists

You define a test case list by entering multiple values for each passed parameter of a test case definition. At test execution, vTESTstudio automatically generates a list of those test cases which either use every parameter value at least once or any combination of parameter values.

Show more

Test Data

Test Data

The data with which a test case is to be executed several times can be defined in different ways: On the one hand, direct input in the test table editor is possible. Both, individual values and ranges with a certain step size, can be specified. On the other hand, the test data can be defined in the Parameter Editor or in the Classification Tree Editor. This allows, for example, a dedicated consideration of limit values or the use of variant-dependent values or value lists.

Test Execution

Test Execution in CANoe

Execution of tests in CANoe

Tests defined in vTESTstudio are configured and loaded in CANoe, executed in real time, and documented in a detailed test report.

In the Test Trace Window you can observe and analyze a test during the test run. The possibility to directly navigate from the Test Trace Window to the corresponding position in the test design in vTESTstudio additionally simplifies the test run analysis.

Show more

CANoe Test Report Viewer

CANoe Test Report Viewer

During test execution in CANoe an automatic detailed reporting takes place. The report can be opened and analyzed with the CANoe Test Report Viewer. Supported are different views on the test data, filtering on various aspects, grouping by verdict, queries on linked trace items etc., and much more. Navigation from a test step in the CANoe Test Report Viewer to the test design in vTESTstudio is supported as well.

Show more

Traceability

You can use vTESTstudio to trace externally defined requirements and test descriptions during test implementation and in the test report (traceability). This is done using exchange files in an open XML format. As a result, any REQM/TDM system can be used coupled with vTESTstudio.

The information exported from the REQM/TDM system is imported into vTESTstudio and can be linked there to test cases. The linked elements can be requirements or test descriptions. Because these elements are used to achieve traceability, they are designated as trace items.

Requirement-based Workflow

In requirement based testing, the requirements defined in the REQM system are directly imported as trace items into the vTESTstudio project and linked to test case implementations there. An n:m link is possible.

Show more

Test-case-based Workflow

If the TDM system already contains a specification of the test cases in prose, the test case specifications are imported as trace items into the vTESTstudio project. There, each test case specification is linked 1:1 to a test case implementation.

Trace Item Explorer

Trace Item Explorer

All trace items imported into a vTESTstudio project are available via the Trace Item Explorer. From there, they can be easily linked to test cases using drag & drop. In the REQM/TDM system, requirements and test descriptions might be structured in hierarchical folders or comparable elements. These folders are displayed in the Trace Item Explorer in the same hierarchy. However, folders cannot be directly linked to test cases.

Show more

Traceability Matrix

You can use the vTESTstudio to trace externally defined requirements and test descriptions during test implementation and in the test report (traceability). This is done using an exchange file in a predefined open XML format. As a result, any REQM/TDM systems can be used coupled with vTESTstudio.

The information (Trace Item) exported from the REQM/TDM system is imported into vTESTstudio and can be linked there to test cases. An overview about the test design coverage is given by the Traceability Matrix. For each trace item linked to a test case, the test report contains a corresponding reference at the test case. This enables traceability from the test case result back to the requirement or test description.

Overview of the Vector Polarion Connection Utility

Get a schematic overview how to achieve traceability between Siemens Polarion ALM, CANoe and vTESTstudio with the help of the Vector Polarion Connection Utility.

Show more

Tool Demonstration: Requirement-Based Workflow

Vector Polarion Connection Utility: Requirement-Based Workflow

Learn to know in a step-by-step tool demonstration how the Polarion Connection Utility can be used to achieve traceability between Siemens Polarion ALM, CANoe and vTESTstudio using the requirement-based workflow.

Show more

Tool Demonstration: Test-Case-Based Workflow

Vector Polarion Connection Utility: Test-Case-Based Workflow

Learn to know in a detailed tool demonstration how the Polarion Connection Utility can be used to achieve traceability between Siemens Polarion ALM, CANoe and vTESTstudio using the test-case-based workflow.

Overview of the Vector Integrity Connection Utility

Get a schematic overview how to achieve traceability between PTC Integrity Lifecycle Manager, CANoe and vTESTstudio with the help of the Vector Integrity Connection Utility.

Show more

Tool Demonstration: Requirement-Based Workflow

Vector Integrity Connection Utility: Requirement-Based Workflow

Learn to know in a step-by-step tool demonstration how the Integrity Connection Utility can be used to achieve traceability between PTC Integrity Lifecycle Manager, CANoe and vTESTstudio using the requirement-based workflow.

Show more

Tool Demonstration: Test-Case-Based Workflow

Vector Integrity Connection Utility: Test-Case-Based Workflow

Learn to know in a detailed tool demonstration how the Integrity Connection Utility can be used to achieve traceability between PTC Integrity Lifecycle Manager, CANoe and vTESTstudio using the test-case-based workflow.