ecu.test on Linux

A separate installer with the file extension “.deb” is available for the installation of ecu.test on Linux systems.

ecu.test Linux Runner offers the possibility to use artefacts (e.g. packages, projects, etc.) from previously created workspaces on a Linux system. However, ecu.test Linux Runner is headless, i.e., without a graphical user interface. Therefore, control is via the REST API.

ecu.test Linux Runner can run in different environments:

  • Physical Machines

  • Virtual Machines

  • Docker

  • Windows Subsystem for Linux (WSL)

Specfic usage is described in the following tutorial: Tutorial Basisworkflow on Linux

Tool Server can be used to connect to tools on a Linux system. More information about the Tool Server can be found in the following section: Tool Server

Note that Tool Server also does not offer a graphical user interface on Linux systems, but its usage is described in the following tutorial: Tutorial ecu.test Tool Server on Linux

System Requirements

  • Operating System: Ubuntu Linux 24.04 LTS AMD64 (support for Ubuntu 20.04 and 22.04 ends with version 2026.1)

  • Minimum Free Storage Space: 3 GB

  • Minimum System Memory: 4 GB recommended 8 GB

Dependencies

  • libcap2-bin

  • libatomic1

  • libsdl1.2debian

  • libgtk-3-0

  • libpcre2-32-0

  • libusb-1.0-0

  • libsm6

  • libnotify4

  • libmpc3

  • libmpfr6

  • libgmp10

  • libjpeg62

  • libopenjp2-7

  • libpng16-16

  • libgif7

  • libwebpmux3

  • libsndfile1

  • libportaudio2

  • libxtst6

  • netbase

  • libc6

  • libcrypt1

  • zlib1g

  • libncursesw6

  • libsqlite3-0

  • libtinfo6

  • libuuid1

  • libwebkit2gtk-4.1-0

Installation

The installation of ecu.test on Linux is done using the “apt” package manager. First the installer file must be transferred to the Linux system; then the installation is executed with the following command:

apt install <path_to_installer.deb>

Required dependencies are installed automatically by the package manager. The installation is stored in the following directory:

/opt/ecu.test-<version>

Handling Multiple Versions

During installation, it is automatically detected whether other versions of ecu.test are installed on the system.

Depending on the installed version number, the installer behaves differently. ecu.test uses the following versioning scheme, where the “patch” component is optional:

<major>.<minor>.<patch> (ex: ecu.test-2024.1)

The following describes the respective behavior given certain conditions of the system during installation:

No Existing Installation of ecu.test

Conditions:

  • ecu.test is not installed on the system.

  • The version ecu-test-2025.3 will be installed.

Behavior:

ecu.test 2025.3 will be installed. No further action.

Older Existing Installation of ecu.test (parallel installation)

Conditions:

  • There is an older version of ecu.test installed on the system which has a smaller major and/or minor version, e.g. ecu.test 2024.1

  • The version ecu.test-2024.1 will be installed.

Behavior:

ecu.test 2022.3 is installed. The old installation of ecu.test 2022.2 remains installed and usable.

The latest version is always stored in the system path during installation. For selection of a specific version, “update-alternatives” can be used.

Updating an Existing Installation of ecu.test

Conditions:

  • There is an older version of ecu.test installed on the system, which has a smaller patch version, e.g. ecu.test 2025.3.1

  • A newer patch version will be installed, e.g. ecu.test 2025.3.5

Behavior: The older version of ecu.test will be uninstalled before the newer version of ecu.test is installed. This behavior also applies to the installation of feature sets.

License Server Setup

Using ecu.test Linux Runner requires a valid license. A license server is automatically queried for a valid license over the network. To specify the license server, it is necessary to set the following environment variable once before the first start of ecu.test Linux Runner (note that the characters are case sensitive):

export tracet_LICENSE=5053@<Hostname_of_License_Server>

More Information

More information on using ecu.test Linux Runner and Tool Server on Linux can be found in the previously linked tutorials. Note that available console parameters can be output with “--help”:

ecu.test --help