Speaks fluently Automotive
ecu.test masters test automation
and you focus on important tasks
ecu.test ['e: 'tse: 'u: 'tɛst] is our tool for testing automotive software. You can connect it to numerous tools and you can also easily integrate it into your workflow.
ecu.test at a glance
- Read and process data in any common automotive format
- ARXML, DBC, A2L, ODX
Connects tools across manufactures
- Connect 70+ Tools, e. g. MATLAB/Simulink, ControlDesk, ModelDesk, INCA, CANape, CANoe, LABView, EDIABAS, FMI, CarMaker, CARLA, Silver, Octane, ALM, IBM ETM
- Looking for your tools? Take a look at our data sheet
- We can also integrate your in-house solutions
Graphically guided test case creation
- Test case creation via Drag & Drop
- Creation of generic test cases for all development stages (MiL, SiL, HiL, ViL)
- Extensive parameterization and configuration options
Can be extended indefinitely
- API first – you can connect everything via API
- Python-based - easily customize your tests in ecu.test to your needs
Generates structured results
- Recording and synchronization of data from different tools
- Creation of test reports in any format
- Graphical representation of signal data
High-performance signal analysis
- Simply add signals using drag & drop
- Recording and evaluation of signals from different sources
ecu.test in detail
ecu.test can read and process data in any common automotive format.
Whether ARXML, DBC, A2L or ODX, our tool speaks virtually all automotive languages fluently. The required format is stored in the test configuration and thus ensures Ethernet and bus signals access to the system-under-test. When reading, the data is parsed and can be integrated into any test case. In the same way, all interactions such as reading, writing, recording and analyzing in the test case can be easily formulated by linking expectations to them.
To ensure that the test is not over after one execution, test cases created once in ecu.test can be reused universally – from project to project, from test environment to test environment.
Due to the generic test description, the test cases created are largely independent of specific hardware and software of the test environments. This means that they can be used repeatedly in various test areas (MiL, SiL, Hil, ViL) and test domains (powertrain, infotainment or ADAS) in a versatile manner.Once created, simply take the test cases with you and reuse them from test environment to test environment, from one project to the next, or from tool to tool. Tests and variants can be saved and reused across all test stages.
For all E/E components and systems in the vehicle, the signal curve can be recorded over the duration of a test case. With ecu.test this is not only easy, but also fast.
Nothing works without signals in sensors, electromechanical components, convenience electronics, bus systems or engine management. The list of possible signals is long, but ecu.test helps you to handle them all easily.As soon as a relevant tool is configured, everything is already prepared in the background. You do not need detailed knowledge of specific protocols. ecu.test can call any signal from a model. Once the required signals are identified, you simply add them via drag & drop. ecu.test then starts recording the signals as soon as the tool is started. That's it.
ecu.test is one of the few tools that can be used across manufacturers. It is also universal and can be used throughout the industry.
With ecu.test, more than 60 tools can be connected via standardized accesses and fully integrated tool interfaces. In this manner we want to prevent testers from creating innumerable complex test cases which they can only use with one tool. Instead, we ensure that ecu.test communicates with all tools and that test cases, once created, can be easily reused. The exchange of the individual tools takes place via abstract tool connections in the form of ports.ecu.test is based on Python. This is ideal for your own solutions and extensions, because ecu.test can be quickly and easily tailored to your own needs, whether for test case development or for integrating other tools.
Sometimes the functional conditions are not adequate for highly specialized solutions. With Python you have the possibility to adapt ecu.test to your own needs and to extend the functionality even further. Thanks to the simple syntax, even very complex requirements in test case development or trace analysis can be easily implemented.With user-defined Python scripts, additional tools can also be integrated with little effort. This applies to special tools and in-house workflows as well as to in-house solutions or in-house hardware. Of course, we'll be happy to do that for you, too. Just send us a message!
ecu.test is so much more than pure test automation. All test results are logged during the test execution and thus form the basis for automatically creating a detailed test report.
View > analyze > evaluate > done.
Test reports are generated automatically after the test cases have been executed. For us, this is normal and simply part of the package. Without extra steps, the information is added to the test report as and when a test case is executed. This forms the basis for reviewing a test execution. Test case-specific, procedural or even infrastructural discrepancies can thus be identified and errors that have occurred can be quickly rectified. When it comes to reporting, we offer maximum scope for customization. Include your own templates and get a report in your design. The export format can also be selected. HTML, JSON, Excel or Text – thanks to the Report API, almost anything is possible. In combination with test.guide you can also easily manage, analyze and re-evaluate the created test reports in ecu.test. The test reports can be automatically uploaded to test.guide on request.
ecu.test use cases
Use Case #1
Test automation with ecu.test at Mercedes-Benz
At Mercedes-Benz, ecu.test has been successfully used for test automation in different test environments (XiL) for years. For this purpose, together we have developed an integrated test methodology for system tests, which is based on two columns: generic test cases and the flexibility of ecu.test.
The result: we reduced the effort required and at the same time, we significantly increased the comparability of the test cases.
Use Case #2
Optimization of virtual parameter measurement
Together with one of our customers, we reduce the measurement time of the engine map on the test bench by 75%. How? By parallelizing the test execution and outsourcing the analysis to test bench-independent resources.
Due to the customized integration of ecu.test, three quarters of the time resources are now free, which can be used for other purposes in the future.
Figures, data, facts?
ecu.test data sheet
Here you will find all interfaces, formats and tools, which you can connect with ecu.test, summarized in one document.
You want to learn how to make the best use of ecu.test and how to integrate the tool into your own processes? Get trained.
Trainings
Trainings
You are interested in concrete application examples? Then click through our product demos.
Product demos
Product demos
We are constantly refining both ourselves and our software. We have compiled the highlights at a glance for you.
Release news
Release news
In case we couldn't convince you in a hurry or you would like to test the software, then contact our sales team.
Contact
Contact