trace.check Release 2026.3

Highlights at a glance

ecu.test agent chat

When creating test steps, a lot of contextual knowledge sits implicitly within the project and has to be taken into account manually for every single step. This takes time, creates inconsistencies, and is prone to errors.

With the ecu.test agent chat, AI support comes directly into ecu.test and addresses exactly that. It handles repetitive work when creating test steps, delivers consistent results, and answers questions about ecu.test and trace.check. That frees up more time for what really matters: the actual test logic.

AI-powered test step generation

The agent assists in creating test case steps and generating trace analysis steps. In both cases, it automatically analyzes the existing project context, taking into account:

Signal mappings, tool and port jobs, and package mappings
Package variables and global constants
The block description as the basis for suitable test steps

Because the agent works directly with the entire project setup, the generated steps fit your existing test environment and are usually ready to use right away. This significantly reduces manual errors when selecting signals, mappings, or package calls.

Note:Support for trace analysis is still in an early stage of development and will be expanded further in upcoming releases.

Consistency through reference implementations

The agent learns from similar blocks in existing packages. Proven test patterns from your own project are incorporated into the generation process and applied to new test cases. This results in consistent and standardized recurring solutions without requiring active intervention from teams.

Customizable generation

Generation can be flexibly adapted to project-specific requirements:

Configurable filters control how many elements from each category are included
Custom instructions allow for adaptation to project-specific naming conventions, style guidelines, and individual preferences

Help right in the chat

Not sure how a specific feature works or how to solve a problem? Just ask in the chat - the agent will help you without ever having to leave your environment.

Workspace compatibility between different trace.check versions

Starting with trace.check 2026.3, running different versions of trace.check in parallel within the same workspace will be significantly easier. This is particularly helpful in environments where multiple teams share a workspace, such as library workspaces, and were previously forced to roll out updates simultaneously across the organization.

In the workspace settings, you can now specify an trace.check version with which the artifacts in the workspace should remain compatible. When saving, trace.check checks the artifacts against this target version, thereby preventing them from accidentally becoming incompatible with older versions. A dialog box alerts the user if an incompatibility cannot be avoided. Additionally, the Workspace Explorer directly displays which trace.check version the artifact or library is compatible with.

Further additions:

A new migration wizard (see Help - Migration helper) conveniently updates an entire workspace to a new trace.check version, eliminating the need to open and save each artifact individually.
The Object API has been updated accordingly so that saving packages via the API also takes the compatibility setting into account, making the feature fully usable in automated workflows.
Comprehensive user documentation covers setup, recommended procedures for version upgrades, handling shared workspaces, and limitations.

ecu.test Interface Python Library

The new ecu.testInterface Python Library provides the public Python interfaces for developing custom trace.check extensions. This makes it much easier to develop your own extensions for trace analyses in an external IDE such as VS Code or PyCharm.

The library is provided as a Python wheel and includes API documentation as well as usage examples.

Modern IDEs enable autocompletion, including inline help. This also allows AI coding assistants such as GitHub Copilot or Claude to better support developers when creating, modifying, or validating trace.check extensions.

Its use is described in detail in the trace.check user documentation and currently includes the following API components:

You can find information about all new features, extensions, and improvements in this release in our Release Notes and in the Changelog.

Changelog