ecu.test on Linux¶
ecu.test is also available for Linux. As with Windows, there are two versions:
ecu.test Linux GUI with a graphical user interface (GUI)
ecu.test Linux Runner without a graphical user interface
Installation¶
For installation under Linux, a Linux installation file with the extension .deb is required.
The ecu.test Linux GUI is contained in the installation file with the suffix _gui.deb.
The ecu.test Linux Runner is included in _runner.deb and _gui.deb.
Installation under Linux is performed using the “apt” package manager. For this, the corresponding installation file must first be transferred to the Linux system. The installation is then 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>
License Server Setup on Linux¶
A valid license is required to use ecu.test. The license and license options are preferably
managed and configured via the License Manager.
The License Manager stores its configuration in the license.ini (see Configuration of license environment variables (Linux only)).
As an alternative to the License Manager, the license variables for the current user can also be
specified manually in the license.ini.
Furthermore, it is possible to provide the license information via the environment variables mentioned in the License Manager section. The following example shows how to set the license server:
export TRACET_LICENSE=5053@<license_server_hostname>
Important
The configuration from the license.ini, if present, takes precedence over any environment variables.
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 2026.3.1)
The following describes the respective behavior given certain conditions of the system during installation:
Initial installation¶
- Conditions:
ecu.test is not installed on the system.
The version ecu.test 2026.3 will be installed.
- Behavior:
ecu.test 2026.3 will be installed.
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 2025.4.
The version ecu.test 2026.3 will be installed.
- Behavior:
ecu.test 2026.3 is installed. The old installation of ecu.test 2025.4 remains installed and can be used via the absolute path
/opt/ecu.test-2025.4/ecu.test.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¶
- Conditions:
There is an older version of ecu.test installed on the system, which has a smaller patch version, e.g. ecu.test 2026.3.1
A newer patch version will be installed, e.g. ecu.test 2026.3.5
- Behavior:
The older version of ecu.test 2026.3.1 will be uninstalled before the newer version (ecu.test 2026.3.5) is installed. This behavior also applies to the installation of feature sets.