Extensions

Although a wide range of functions is provided with installation it may become necessary in certain cases to extend the functionality of ecu.test. A variety of possibilities can be used, but that requires knowledge in Python programming.

  • User Python library - simple

    • Particularly well-suited for file management and calculation

    • Will not appear in test report

    • Have no dialog of their own

  • Custom checks - simple

    • Custom checks for packages, projects and analysis packages

    • Optional custom fixes in the check dialog context menu

  • External Python libraries - simple

    • allows the integration of external Python libraries not included in the scope of installation of ecu.test.

  • User-defined utilities

    • Clear distinction between AXSUtility and UserUtility

    • Cannot be mapped (see mapping)

    • AXSUtility - simple

      • Definition of an interface

      • Data management, dialogs and report are generated from there

    • UserUtility - complex

      • Own data management

      • Own dialogs

      • Own report

  • User-defined tools - simple

    • Definition of a custom tool

    • Data management, dialogs and report are generated from there

    • Can be mapped (see mapping)

    • Settings are test-bench specific

  • User test management adapter - complex

    • Interface for communication between ecu.test and test management system

    • Own test management adapter

    • Implementation is specific to the use case

  • Parameter generator for projects - complex

    • Generator creates parameterization during runtime and passes it to a package.

    • After parameterization a package is carried out directly before the next parameterization takes place. That allows evaluating return values of a preceding run and considering the results in the next one.

    • Own data management

    • Own dialogs

    • No own report

    • Generators can be tested “offline”

  • Package generator for projects - complex

    • Generator creates packages during project execution and executes them immediately.

    • Own data management

    • Own dialogs

    • No own report

    • Generators can be tested “offline”

    • Possibility to use the Object API

  • Project generator - complex

    • Generator creates subprojects during project execution and executes them immediately.

    • Own data management

    • Own dialogs

    • Generators can be tested “offline”

    • Possibility to use the Object API

The following methods can be imported from the package log in the extensions to print information to the log window of ecu.test.

  • SPrint(text)

    Prints out a blue-colored message.

  • WPrint(text)

    Prints out a yellow-colored message (warning).

  • EPrint(text)

    Prints out a red-colored message (error message).

from log import SPrint, WPrint, EPrint

SPrint('This is an info')
WPrint('This is a warning')
EPrint('This is an error')

Shared Libraries

Some extensions for ecu.test can’t be implemented in Python. They must be provided as a dynamic linked library (DLL) or shared library (SO). This is the case, if the extension communicates with a low-level hardware tool or if the performance is important.

  • Time synchronization via a shared library - complex

    • By adding a shared library the time can be synchronized in selected diagnostics- and bus-ports

    • A shared library can be used as a time source in ecu.test while executing a test case