hero image
Complementary modules for our tool chain
In addition to our software products, we also offer a number of enhancements that increase their functional scope or expand their areas of application. We have listed them here under the term “extras”, even if they complement our tools quite differently.

auto.spy analyzer for ecu.test

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 basic functions of the auto.spy viewer. If this is not enough, the auto.spy analyzer for ecu.test helps you analyze your result data further. In addition to viewer functions, this also includes
  • importing, exporting and printing of signal data
  • fast event search using simple, logical signal conditions
  • script-based signal analysis for more complex problems
  • time shifting of signals as well a
  • creating and deleting signal groups
More details about the key features are available in our data sheet.

ecu.test diagnostics

Automated use of diagnostics functions for vehicles

Access to diagnostic systems is a key component of many test cases in the automotive environment. What we want to do with the ecu.test diagnostics is to enable test-case developers to use diagnosis functions without having detailed knowledge of the specific protocols. No extra diagnostic tools are necessary.

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.
ecu.test diagnostics
More details of the scope of functions and the standards supported are available in our data sheet.

ecu.test diagnostics data sheet

Jenkins Plug-in

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


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 (QKit) jointly developed with the VALIDAS company 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.

1a) Requirement-based testYES++++++++
1b) Interface testYES++++++++
1c) Fault injection testYES++++++
1d) Ressource usage testYES+++++
1e) Back-to-back comparison test between model and code (if applicable)YES++++++

+ necessary, ++ mandatory

Certified safety for your products

The application of the QKit automates the qualification process, thereby illustrating the reliability of the qualified toolecu.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 QKit

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 QKit 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).
QKit 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
  • Descriptions of test cases for 3rd party tool connections based on ecu.test port concept