Basic Workflow on Linux Tutorial¶

The aim of this tutorial is to convey how ecu.test Linux Runner works. An example workflow is provided and references are made to the relevant sections of the user manual.

Step 1: Prepare the workspace¶

ecu.test Linux Runner does not have a GUI to create Workspaces. Therefore, the workspace must be created in Windows with ecu.test and then transferred to the computer on which the ecu.test Linux Runner is operating, a version control system can be used for this such as git. Alternatively, if a workspace already exists, it can be copied and similarly moved.

Step 2: Start ecu.test Linux Runner¶

For the rest of the tutorial, it is assumed that the Linux user is tracetronic and the workspace is in the following path: /home/tracetronic/workspace.

To start ecu.test Linux Runner, the command ‘ecu.test’ must be executed in a console and the workspace must be passed as a parameter.

ecu.test --workspaceDir /home/tracetronic/workspace

ecu.test Linux Runner started successfully when the message “REST API now available at 127.0.0.1:5050” appears in the console output.

Step 3: Control ecu.test Linux Runner with the REST API¶

The REST API must be used to control ecu.test Linux Runner. Further REST API information is available in the REST API Documentation. While ecu.test Linux Runner is running, interactive documentation can be found at http://127.0.0.1:5050/api/v2/ui. What follows is an example of running a package, simplepackage.pkg, without TBC and without TCF:

curl -X 'PUT' \
  'http://localhost:5050/api/v2/execution' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "tbcPath": "",
  "tcfPath": "",
  "testCasePath": "simplepackage.pkg"
  }'

For the ecu.test Linux Runner to be able to access the REST API remotely, ecu.test Linux Runner can be started with an extra parameter:

ecu.test --workspaceDir /home/tracetronic/workspace --restApiEnableRemoteAccess

The port can be set with the parameter –restApiPort PORT (default: 5050).

Step 4: Evaluating Results¶

The Rest API’s ‘execution’ endpoint can be used to get the directory for the test report.

For example:

curl -X 'GET' \
 'http://localhost:5050/api/v2/execution' \
 -H 'accept: application/json'

Response:

{
  "order": {
    "executionId": "",
    "tbcPath": "",
    "tcfPath": "",
    "testCasePath": "simplepackage.pkg"
  },
  "result": {
    "reportDir": "/home/tracetronic/workspace/TestReports/simplepackage_2022-01-01_133700",
    "result": "SUCCESS",
    "subReportIds": [],
    "testReportId": "1234567-aaa1-bbb2-ccc3-abcd1234a321"
  },
  "status": {
    "key": "FINISHED",
    "message": ""
  }
}

The test report can be evaluated with the Report viewer after the report directory has been transferred. ecu.test Linux Runner saves all outputs in log files. The log files “ECU_TEST_OUT.log” and “ECU_TEST_ERR.log” are in the following folder:

/home/tracetronic/.cache/ecu.test 2026.3/