When a quick glance is not enough

The offline trace analysis of ecu.test processes recorded signal traces automatically. In the process, new derived signals are sometimes calculated. Reports with analysis for the tested cases are generated from the information.

The signal data and test case analysis are interactively visualized using the trace.xplorer basic by default. If this is not enough, the trace.xplorer helps you analyze your result data comprehensively. Compared to the basic version, it offers additional features such as

• importing, exporting and printing of signal data
• deleting unneeded signal data from existing documents
• fast event search using simple, logical signal conditions
• script-based signal analysis for more complex problems
• time shifting of signals as well as
• creating and deleting signal groups
• configuring additional Wireshark capture interfaces

More details about the key features are available in our data sheet.

trace.xplorer data sheet

AI-powered test case implementation

Want to know more?

ecu.test agent fact sheet ecu.test agent webpage

Simple and fast access to measurement and calibration quantities without additonal tools

In order to detect errors in the program logic of an ECU function, whitebox tests can be performed. This type of test requires access to the internal variables and signals to measure, calibrate and evaluate them during program execution.

In the automotive sector, measurement and calibration protocols are used for this. ecu.test did not previously support them directly, but instead outsourced this task to various 3rd party tools, which were only controlled by ecu.test. With the extension ecu.test calibration, basic measurement and calibration access without additional tools is now possible.

The current range of functions includes the widely used XCP protocol with the following functions:

• Ethernet access via TCP and UDP
• Reading and writing of measurement and calibration variables
• Recording and analysis of variables in MDF4 file format

More details of the scope of functions and the standards supported are available in our data sheet.

ecu.test calibration data sheet

Python power for automotive testing

The ecu.test code consists of a Python library, a Visual Studio Code extension, and a pytest plugin. Together, these components provide lightweight access to all the tools, automotive interfaces, and test quantities supported by ecu.test via code completion.

Advantages

• A lightweight API that can be used without prior knowledge of ecu.test.
• Easy access to over 80 automotive tools and various data formats, such as A2L, DBC, and ARXML
• Auto-completion and inline help in Visual Studio Code
• Flexible integration into CI environments and Python test frameworks, such as unittest, pytest, ...
• pytest plugin for seamless integration of test reports into test.guide
• Compatible with Linux and Windows

How to get started with ecu.test code

• Have a licensed version of ecu.test (2025.3 or newer) ready
• Install Python 3.12
• Setup ecu.test code

You can find more details about the tool in the user documentation.

ecu.test code user documentation

Automated use of diagnostics functions for vehicles

Access to diagnostic systems is a key component of many test cases in the automotive environment. Our solution is based on intuitive test steps resulting from close cooperation with experienced system engineers. Typical use cases, such as the checking for specific error-memory entries and the reading and writing of diagnostic data, can thereby be more efficiently realized.


More details of the scope of functions and the standards supported are available in our data sheet.

ecu.test diagnostics data sheet

Intuitive access to complex test benches – even without expert knowledge

ecu.test lab offers particular advantages in the early development phases and for exploratory testing in SiL environments because processes can be easily tracked in real time despite the lack of a GUI. Due to the separation of the user interface and technical control, the behavior of a test bench as well as the software under test can be visualized and controlled without requiring in-depth technical knowledge of the test environment.

Whether Windows or Linux, local or remote, CAN, XCP, model or multimedia – ecu.test lab runs where you need it and communicates via all interfaces available in ecu.test. Directly based on existing mappings or packages.


You need more information? Click here:

ecu.test lab webpage ecu.test lab help

Easy integration of ecu.test into the Jenkins CI environment

Our approach for testing is based on an easy integration of ecu.test into Jenkins continuous integration environment. We have developed a plug-in to enable the Jenkins automation server to initiate ecu.test test cases with the corresponding configuration event-controlled or time-triggered. This allows the test process to be flexibly adapted to the specific circumstances in the company and the requirements of the development team and the project.

The ecu.test test runs triggered by Jenkins can be distributed flexibly to the currently available HiL test benches and can be carried out automatically. This also utilizes the test benches at times when there are no test engineers on site (so-called "nightly tests").

Key features at a glance:

• Open source Jenkins plug-in
• Easy integration and control of ecu.test and the tool server
• Allows for the execution of ecu.test packages and projects with the corresponding test configuration
• Continuous feedback on the integrated test result display in different report formats
• Connection to test.guide for report management
• Parsing of ecu.test logs after warning and error messages
• Subsequent report generation and trace analysis

Click here for the Jenkins Plug-in

ISO 26262-compliant testing with ecu.test

ISO 26262 is a ISO standard specifically tailored for the automotive industry for safety-relevant electrical and electronic systems in mass-produced vehicles. The procedure model it describes and the methods listed in relation to development and production are intended to ensure the functional safety of the corresponding systems.

An integral part of this procedure model is the tool qualification, which is designed to prevent faults reaching the product thereby developed by the use of such tools. The qualification kit (Q-Kit) for our ecu.test test automation tool provides a fast and flexible ISO 26262 qualification for its use in tool chains for the development of functions with safety requirements up to the ASIL D level.

Certified safety for your products

The application of the Q-Kit automates the qualification process, thereby illustrating the reliability of the qualified tool ecu.test for defined and documented use cases.

The consideration of the entire tool chain and the classification for every tool is the starting point of the tool qualification in accordance with the ISO 26262 standard.

Advantages of the ecu.test Q-Kit

The ecu.test Qualification Kit follows a model-based concept for classification and qualification. This concept allows the tool to be systematically analyzed and the features based on the use case of the development/test process to be considered. An additional extension able to reuse existing tests and validation steps, is also possible.

A qualification support tool included in the Q-Kit guides the user through the qualification and creates all necessary documents. The application results are a Tool Qualification Report and a Safety Manual documenting the qualification process and restrictions for the planned use cases of the tool (ecu.test).

Q-Kit components

• A wizard (Qualification Support Tool - QST), which guides the user through the qualification process and creates the qualification documents from the templates
• Tool Classification Report
• Tool Qualification Plan
• Tool Qualification Report
• Tool Safety Manual
• Test suits for automated test cases
• Analysis of potential errors, mitigations and test descriptions for selected ecu.test features and test steps, e.g.
• Automated execution
• Result calculation
• Reporting
• Configuration (e. g. mapping)
• Language elements of tests for logic, control flow, validation and expectations
• Descriptions of test cases for 3rd party tool connections based on ecu.test port concept
• Application manual

I'd like to get the Q-Kit