ECU-TEST

ECU-TEST is a software tool developed by TraceTronic GmbH, based in Dresden, Germany, for test and validation of embedded systems. Since the first release of ECU-TEST in 2003,[1] the software is used as standard tool in the development of automotive ECUs[2][3][4] and increasingly in the development of heavy machinery[5][6][7] as well as in factory automation.[8] The development of the software started within a research project on systematic testing of control units and laid the foundation for the spin-off of TraceTronic GmbH from TU Dresden. ECU-TEST aims at the specification, implementation, documentation, execution and assessment of test cases. Owing to various test automation methods, the tool ensures an efficient implementation of all necessary activities for the creation, execution and assessment of test cases.[9]

ECU-TEST
Developer(s)TraceTronic GmbH
Stable release
2020.2 / May 2020 (2020-05)
Operating systemWindows
Available inEnglish and German
TypeTest automation, Test software, Data acquisition
LicenseProprietary software
Websiteecu-test.com

Functionality

Methodology

ECU-TEST automates the control of the whole test environment and supports a broad range of test tools. Various abstraction layers for measured quantities allow its application on different testing levels, e.g. within the context of model in the loop, software in the loop and hardware in the loop as well as in real systems (vehicle and driver in the loop). Creating test cases using ECU-TEST is conducted graphically and does not require programming skills. Test-case descriptions have a generic form, which together with extensive parameterization and configuration options, allows uniform access to all test tools and thereby simplifies re-use of existing tests over multiple development phases.

Structure

ECU-TEST is organized in four parts:

  • Editor and Project manager
  • Configurator
  • Test engine
  • Analyzer and Protocol generator

In order to create a test case, one or more sequences of test steps and their parameterizations are specified using the editor. Test steps comprise reading and evaluating measured quantities of the test object, manipulating the test environment as well as the execution of diagnostic functions and control structures. Multiple test cases can be organized using the project manager. Additional settings for test object and test environment can be made using the configurator. The execution of test cases is performed using a multi-stage test engine. The generated log data serve as the basis for the creation of test reports. Subsequent to the test execution, optional checks of recorded measured quantities are performed in the analyzer. From the results of test-execution and subsequent checks, the protocol generator produces a detailed test report, which is displayed interactively and can be archived in files and data bases.

Interfaces

ECU-TEST provided clear interfaces for extensions and for the integration in existing test and validation processes. A large amount of test hardware and software is supported by default. Using user-defined test steps, plug-ins and Python scripts, additional tools can be integrated with little effort. Via a specific client-server-architecture, software tools of multiple test-bench computers in distributed test environments can be addressed. Using a COM interface, further tools, e.g. for requirements management, revision control and model-based testing can be integrated. ECU-TEST supports the following hardware and software tools and is based on the following standards:[10]

Supported hardware and software

Test management tools
  • HP ALM
  • Micro Focus Octane
  • CA Agile Central (Rally)
  • SIEMENS Polarion
  • IBM RQM
  • PTC Integrity LifeCycle Manager

Source code management tools
gollark: Why would you want to? What login prompt? Bees?
gollark: Brute-force all possible combinations of vowels.
gollark: Guess randomly based on your school name?
gollark: It doesn't HAVE to be saved anywhere.
gollark: Personally, at least, I don't really care about consistency, and the individual UIs I use look/function nicely.

References
  1. H.-C. Reuss, R. Deutschmann, J. Liebl, F. Munk, C. Schmidt: Automatic ECU Test with HiL-Simulation. 5th Stuttgart International Symposium on Automotive and Engine Technology“. Expert, 2003.
  2. Rocco Deutschmann, Frank Günther, Matthias Roch, Hans-Christian Reuss, Frank Kessler, Wolfram Bohne, Carsten Krug: New strategies and solutions for automated test of embedded software. 6th Stuttgart International Symposium on Automotive and Engine Technology. Expert, 2005.
  3. Wolfgang Schlüter, Franz Dengler: HiL-Testsysteme für den BMW Hydrogen 7. 7th Conference on „Hardware-in-the-Loop-Simulation“. Haus der Technik, 2007.
  4. Daniel Brückner, Michael Kahle: OTX als Test- und Applikationssprache in der On-Board-Diagnose. 6th Conference on „Diagnose in mechatronischen Fahrzeugsystemen“. Expert, 2012.
  5. Thomas Neubert, Rocco Deutschmann: Automated software test using HiL technology. 13th ITI Symposium, 2010.
  6. Thomas Borchert, Rocco Deutschmann, René Müller, Andreas Abel, Torsten Blochwitz: Simulation and Testing of Off-Road Vehicles in Virtual Reality - Development of a Validation Framework for Multi-Purpose Vehicles. 13th ITI Symposium, 2010.
  7. Rocco Deutschmann, René Müller, Andreas Abel, Torsten Blochwitz: Simulation and Test of Multi-purpose Vehicles. ATZoffhighway, 2011.
  8. Klaus Kabitzsch, André Gellrich, Jens Naake: Automatisierte Steuerungstests vereinfachen die virtuelle Inbetriebnahme in der Fabrikautomation. atp edition, 2012.
  9. Rocco Deutschmann: Semi-formal methods for the automated test of embedded systems. Doctoral thesis, TU Dresden, 2007.
  10. ECU-TEST data sheet Archived 2013-12-03 at the Wayback Machine (PDF; 372 kB). Retrieved 12 January 2015.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.