ecu.test Release 2025.1

Until now, additional Python libraries could be stored in a configurable directory. However, you always had to make sure that they were not already delivered with ecu.test and that they were intended for the same Python version.

To make it easier to integrate additional libraries, you can now specify your dependencies in a requirements.txt (see pip documentation) in the .workspace directory. ecu.test then installs the libraries either selectively or when the program is started, and also checks compatibility with the libraries already delivered.

The ecu.test Runner is now also available for Windows. 
It is perfect for use in Continuous Integration (CI) environments, as well as integrated development environments (IDEs) and other applications where a GUI is not required.
With the new Runner for Windows systems, you can achieve both higher performance and reduced CPU and RAM usage, saving resources and costs. It also makes it easy to move to the public cloud.

The Runner is now also automatically available on Windows: ecu.test_runner.exe.
Just like the “normal” ecu.test.exe, this new EXE allows tests to be run via the command line or the REST API.
It can also be used with test.guide to further optimize test execution. All you have to do is to change the path to the runner (ecu.test.exe →  ecu.test_runner.exe) in the ResourceAdapter configuration.

Note: Existing ecu.test licences can still be used for this variant without any modifications.

The file links have been revised so that reports can now be viewed in the TRF viewer by default without the need for an ecu.test license. This reduces loading times significantly. The same applies to reports opened from test.guide.

Double-clicking a report now opens the TRF Viewer (license-free) by default. The toolbar of the TRF Viewer also offers the option to open the report with the ecu.tests Report Viewer. This allows you to use additional functions such as report generators or revaluations.

Note: In the local settings, you can specify whether the reports should always be opened in association with ecu.test.

The ecu.test user documentation has been fully revised to make information faster and easier to access.
The update includes a modern design, an optimized structure and a unified presentation.

The new design relies on clear colors in the tracetronic style and a well-organized layout that allows for intuitive navigation.

All help sections, including the API and TRCP help, have been standardized to ensure a consistent look and feel and improved clarity.

In CI/CT environments there is no need for the GUI functions of TortoiseGit. Until now, however, TortoiseGit was a mandatory requirement for Git support in ecu.test.
In order to enable the documentation of the revision and status of the artefacts used in the report on systems without TortoiseGit, the requirement for TortoiseGit has been dropped.

To support revisions, status and repository in the report, only a git.exe is required in the path environment variable.

Due to the decoupling, support for Git under Linux is now also included. Here too, it is sufficient if the git executable can be found in the path environment variable.

The CAN(-FD) ports of the hardware-related bus connections are now able to write the standard formats ASAM MDF 4 and PcapNG in addition to the ASC format. This means that recordings can be further processed with a variety of other tools without conversion. In addition, these are binary formats, which benefit from lower memory consumption.

The target format can be specified in the test bench configuration in the port and affects the signal recording.

ASC and MDF4 can be processed consistently in the trace analysis. PcapNG with bus communication is currently not supported by the trace analysis.

ecu.test is available as a runner for various target systems to meet the requirements of scaling applications, e.g. virtual testing in SiL environments or trace analysis of real driving data.

This pure execution variant without graphical user interface can be installed on Ubuntu 20.04, 22.04 and now also 24.04 via an ecu.test deb package. In addition to the deb package, Docker files are also available to build Ubuntu-based container images.

With the release of 2025.1, we now also provide a ready-to-run ecu.test image that can be used in container environments and remotely controlled via REST API or CLI.

The capabilities of a runner are not enough for you? You want to edit ecu.test artifacts on Linux as well? No problem! The graphical user interface for Linux is already available as an ALPHA version.
If you are interested, please contact our Support team.