ecu.test Linux Runner¶

The ecu.test Linux Runner has no graphical user interface and is therefore particularly suitable for test automation, as it offers high execution speed and has fewer dependencies due to the lack of a user interface. It can execute artifacts such as packages and projects from existing workspaces on Linux systems. The ecu.test Linux Runner is started via the command line and controlled via the REST API or the Command line (batch interface).

ecu.test --help

Specific usage is described in detail in the Basic Workflow on Linux Tutorial.

Alternatively, ecu.test Tool Server can be used to connect to tools on a Linux system. For more information about ecu.test Tool Server, see the section Tool Server. The usage on Linux is described in the Tool Server on Linux Tutorial.

Installation¶

ecu.test Linux Runner can run in different environments:

• Physical machines

• Virtual machines

• Windows Subsystem for Linux (WSL)

• Docker

Setup for physical/virtual machines or WSL is described in chapter Installation on Linux. The use of ecu.test Linux Runner in a Docker environment is described in the following chapter.

Installation within a Docker container¶

A UBI9 image with the file extension .tar.gz is available, which can be used to start ecu.test Linux Runner in a Dockerfile. Alternatively, a custom image based on Ubuntu can be built using Dockerfile.

Installation¶

1. Transfer the image file to the Linux system.

2. Load the image:

   docker load --input <path_to_image.tar.gz>
   

3. List all images to find out the IMAGE ID of the ecu.test image:

   docker images
   

4. Create and run a container from the image:

   docker run -p 5050:5050 \
   -v <path_to_ecutest_workspace_on_host>:/app/workspace \
   -e TRACET_LICENSE=<license_server_url> \
   <IMAGE ID> \
   --workspaceDir /app/workspace \
   --restApiEnableRemoteAccess
   

   This command does the following things:

   • bind port 5050 of the host system to port 5050 in the container

   • mount the workspace <path_to_ecu.test_workspace_on_host> into the container at /app/workspace

   • set the environment variable TRACET_LICENSE so ecu.test can acquire a valid license

   • start ecu.test in the container and open the workspace /app/workspace

   • enable access to the REST API

The REST API is then available from the host via http://localhost:5050/api/v2/ui.

Packages or projects can also be executed directly using the execute subcommand on the command line:

docker run -p 5050:5050 \
-v <path_to_ecu.test_workspace_on_host>:/app/workspace \
-e TRACET_LICENSE=<license_server_url> \
<IMAGE ID> \
execute --workspace /app/workspace \
--testconfiguration myTCF.tcf \
--testbenchconfiguration myTBC.tbc \
testcase.pkg