...makes automation easy

With ECU-TEST you can intuitively create test cases for automotive software in every development phase and run them automatically – even without any prior knowledge of test automation and programming. We have designed the tool in such a way that the test quality is kept exceptionally high at all levels, although the effort it takes to use it is extremely low.


ECU-TEST allows for a consistent and effective automation of the entire test environment. It supports and connects so many different software tools, that it easily fits in numerous existing test and validation processes.

TraceTronic ECU-TEST Tools


The test automation tool ECU-TEST can be used in all phases of development up to the finished vehicle itself. It allows for a high reusability of the test cases in the various test areas MiL, SiL, HiL, PiL and ViL (vehicle), through generic test description and tool-access abstraction.


We have designed ECU-TEST to integrate perfectly into existing tool chains. For example, the software can be easily embedded in a continuous-integration platform by supporting standards and various interfaces. Customers can also include their own specific tools solutions. Using a number of extension capabilities, we tailor ECU-TEST to fit your exact problem definition.

TraceTronic ECU-TEST Tools
All interfaces, formats and tools at a glance


  • ASAM ACI 1.4
  • ASAM XiL API version 2.0.1 and 2.1.0 (MA, EES, ECUC/M Port)
  • AUTOSAR Classic & Adaptiv
  • DoCAN (ISO 15765-3)
  • FMI 1.0/2.0
  • ISO-TP (ISO 15765-2)
  • KWP2000 (ISO 14230)
  • OSI (Open Simulation Interface)
  • PLP (Probe Logger Protocol)
  • ReqIF 1.2
  • SAE J1939
  • SAE J2534 PassThru
  • UDS (ISO 14229-1)

Bus description:

  • ARXML (Classic Platform) 4.1.1 to 4.4.0
  • ARXML (Adaptive Platform) to 10/18
  • DBC
  • FIBEX to 4.1.1
  • FIBEX for Ethernet 4.1.2
  • Diagnostic Log and Trace: Analyse non-verbose Mode
  • LIN Description File (LDF)

ECU description:

  • ASAP2 Database (A2L)
  • Executable and Linkable Format (ELF)
  • Intel HEX
  • Motorola S19

Supported trace formats:

Signal-based trace formats:

  • AS3TRACE (TraceTronic)
  • ­CSV
  • MAT: MATLAB/Simulink, ControlDesk
  • MDF 3.0, 3.1, 3.2, 3.3, 4.0, 4.1
  • STI, STZ 2.0.1 ASAM XiL-API
  • TDMS: National Instruments


  • ASC (Vector)
  • BLF (Vector)
  • MDF 4.0, 4.1
  • TTL (TTTech)


  • BLF (Vector)
  • DLT
  • PCAP, PCAPNG (TraceTronic, Wireshark)


  • ADTF2
  • eCAL 5.0, 5.1


  • ERD (CarSim)
  • ERG (CarMaker)
  • RDB (VTD)


  • Audio: FLAC, WAV
  • Video: AVI, MP4, MKV, MTS

Other formats supported on request.

Supported hard- and software

  • A&D: iTest
  • AKKA: Gigabox
  • Beckhoff: TwinCAT
  • Digitalwerk: ADTF
  • dSPACE: ControlDesk
  • dSPACE: ModelDesk
  • dSPACE: MotionDesk
  • EA: UTA 12
  • ESI: SimulationX
  • FEP
  • FEP3
  • FEV: Morphée
  • HMS: ACT - Restbussimulation
  • HMS: Bus interfaces
  • IPG: CarMaker
  • JS Foundation: Appium
  • KS Engineers: Tornado
  • Lauterbach: TRACE32
  • MAGNA: BluePiraT
  • Mathworks: MATLAB® & Simulink
  • Mechanical Simulation Corporation: CarSim
  • MicroNova: NovaSim
  • Modelica Association: FMI
  • NI: LabVIEW
  • NI: VeriStand
  • NI: VISA
  • Opal-RT: RT-LAB
  • PLS: UDE
  • RA Consulting: DiagRA D
  • SAE: PassThru
  • Scienlab: CDS
  • Scienlab: ESD
  • Softing: CAN L2 API
  • Softing: DTS
  • Softing: EDIABAS
  • Speedgoat: Simulink RT
  • Synopsys: Silver
  • Synopsys: Virtualizer
  • The GNU Project: GDB
  • TraceTronic: cTestBed
  • TraceTronic: Ethernet
  • TraceTronic: Multimedia
  • TraceTronic: RemoteCommand
  • TraceTronic: Serial interface
  • TraceTronic: SSH
  • TTTech: TTXConnexion
  • Vector: CANalyzer
  • Vector: CANape
  • Vector: CANoe
  • Vector: XL API
  • ViGEM: CCA
  • Vires: VTD
  • VW: ODIS
  • X2E: Xoraya

Test management tools

  • Broadcom Rally Software
  • Micro Focus ALM / HP Quality Center
  • Micro Focus Octane
  • PTC Integrity LifeCycle Manager
  • SIEMENS Polarion ALM
  • Test42

Source code management tools

  • Apache Subversion
  • Git

On request we will gladly realize the linkage of your specific hardware or software.


Many of our clients and partners have a growing desire for smooth cooperation, even within their own ranks. The classical role division is reaching its limits and really inhibits both motivation and innovation. Being an agile organization, we strongly focus on this very aspect. With ECU-TEST, we support, for instance, version control (SVN, Git) and enable various users to use the same workspace. Upon request, different work statutes can be visualized and compared with each other rather effortlessly.

Latest Release 2021.2

Release video

We are constantly refining both ourselves and our software.

In the current release video, our product owner Michael Gebauer shares his personal highlights of the latest ECU-TEST version.

Take a look!

Feel free to click through the features of past versions as well.
Older versions
Want more videos? Then take a look at our YouTube channel.
Would you like to see the latest features? Then browse through our product demos.

Top features at a glance

Use of all supported network protocols with Vector Ethernet measurement hardware

ECU-TEST 2021.2

ECU-TEST supports active and passive network communication for many protocols used in the automotive field. These include service-based communication via SOME/IP, DLT, AUTOSAR Socket Adaptor and many more.

A new feature is the ability to use all of these protocols directly with Ethernet-capable measurement hardware from Vector in a network-based mode. This eliminates the need to connect the measurement hardware to the network card via mirroring mode.

Improved support of service-based communication

In order to extend the usage possibilities of the service-based communication, several new enhancements have been implemented:

  1. Configurable behavior for handling SOME/IP protocol errors and informative reporting
  2. Selectable source ports for active SOME/IP service communication: communication even in firewall-protected networks
  3. Manual control of the ECU-TEST service discovery mechanism for recording and analysis during the startup phase

ECU-TEST Neuerungen 2021.2

Furthermoore, there is access to services even if only the service-consumer relationship is mapped in the (ARXML) description file (ECU extract)

Playbook creation for the Automotive DevOps Platform

ECU-TEST 2021.2

Playbooks are the central element in the Automotive DevOps Platform for the execution of test orders distributed on multiple test benches. Playbooks describe the workspace to be used – including test cases as well as the test bench setup and test bench teardown. Additionally, the three sections Setup, Tests and Teardown can be parametrized using global constants.

With the new feature Generate Playbooks from ECU-TEST, playbooks can be created in the already familiar project editor GUI. By using the already existing TEST-GUIDE connection, they can be uploaded to TEST-GUIDE directly from ECU-TEST.

An included Template project with the given folders Setup, Test and Teardown simplifies the creation of playbooks.

More information on this can be found in the user documentation.

Access to structured signal data for ASAM Open Simulation Interfaces (OSI)

OSI data streams contain complex and also structured signals. For the creation of test cases and analyses, ECU-TEST offers the possibility of using complex structures in the test case and trace analysis in addition to leaf elements. Structures can be read and recorded in the test case, as well as used in trace analysis. Access to the elements of a structure is simplified by an auto-completion mechanism.

The feature can be activated on request. If you are interested, please contact us at

ECU-TEST 2021.2

ASAM XIL: Dummy-Server and TestSuite as support to connect your own tools to ECU-TEST

ECU-TEST contains a tool connector called ASAM XIL which enables you to connect a variety of tools which implement a server interface according to the ASAM XIL-API.

This standard defines the interfaces for model, measurement, calibration and error simulation ports. Using these ports, you can read, write, record and play back stimulation sequences on variables.

The interface is also often used by users of ECU-TEST to connect tools they develop themselves to ECU-TEST.

ECU-TEST 2021.2

To support this, we have created a starter package which is available on demand from our customer support. It contains a working dummy server – including source code – which could be a good foundation for implementing your own server.

To test the compatibility of your server with ECU-TEST, we also provide a TestSuite.

This TestSuite contains a generator to help you to create the configurations and mappings, as well as select the suitable test cases for your server. After executing the generator you will receive a project in ECU-TEST which tests all the core functionality of the ASAM XIL interface and which creates a report document as reference for your level of compatibility.

More flexible test cases using generic job/Image mappings and parameterized library Packages

In many use cases, it is useful to separate the read or write access of a test quantity together with necessary pre- and post-processing in a library Package. If the test quantity is not fixed, but you would like to use the pre- and post-processing for different test quantities, you need to alter the used mapping.

This can be done using global mappings or parameter sets in a project, but is limited to one test quantity per test case as these mechanisms cannot change the mapping within a Package run.

But there is another, more flexible mechanism – parameterized mapping on Package calls. Using parameterized mapping, you can manipulate the mapping to be used within the Package called up.

ECU-TEST 2021.2

This mechanism is available only for those mappings in the library Package which are of a generic type. This means that they do not point to a real target path.

Therefore, the mechanism was not available for jobs and image mappings. This has been changed with ECU-TEST 2021.2. Now you can create a library Package that reads an image mask, preprocesses the read image and applies text recognition. This Package can be used subsequently at any point of the test case. This approach improves the structure of your test cases and prevents redundant implementations of the same logic which lead to unnecessary maintenance work in the long run.

Downstream analysis execution distributed by TEST-GUIDE

ECU-TEST 2021.2

By performing trace analysis downstream, you can release valuable test resources sooner and significantly increase the test throughput of your HiLs/prototypes.

For projects or packages that are executed with downstream analysis, only the test case is initially taken into consideration. The resulting recordings and analysis jobs are passed on to a configured TEST-GUIDE, which distributes the analyses to available infrastructure.

The TEST-GUIDE ResourceAdapter simplifies making ECU-TEST available on physical or virtual machines or in containerized environments. After completion, the results of the analyses are automatically collected in TEST-GUIDE.

In addition to this application scenario, downstream analysis distribution is also available in the Automotive DevOps Platform workflows with playbooks.

New tool connectors for scenario-based testing: DYNA4 and SCANeR

For scenario-based testing, ECU-TEST offers two new tool connectors: DYNA4 from Vector Informatik GmbH and SCANeR from AVSimulation.

DYNA4 is an open simulation environment for virtual test driving. The DYNA4 connector offers the possibility of loading, parameterizing and starting tasks by using tool jobs.

SCANeR provides a simulation platform for creating and executing test scenarios in a virtual environment. The resulting recordings can be fetched and used in trace analysis. For SCANeR, it is possible to control and parameterize the simulation.

ECU-TEST 2021.2

I’ve got to have it!


You think ECU-TEST is a life-changing software? Then get in touch with our sales team and let us make you an offer.

We haven’t convinced you yet or you want to test the software? Contact us and give us a chance to do better.


You want to learn how to make the best use of ECU-TEST and how to integrate the tool into your own processes? Here, you can find out more about our product trainings.

Data sheet (PDF)

Too much useless information and you just need the hard facts? Then download our product data sheet.

Keep me posted!

ECU-TEST technology update to Python 3 and wxPython 4

Dear ECU-TEST users,
in order to keep the product ECU-TEST up to date, it is necessary to update important underlying software technologies and to switch therefor to Python 3. Unfortunately, this new version of the language is not completely backward-compatible. Thus, user with ECU-TEST version lower than 8.0 are also affected, if they want to update their workspaces. In the following migration guide we have summarized the main reasons for the switch to Python 3 and name the most important effects on our users.

Your ECU-TEST team

Python 3 guide