Fast Report Access

Since ECU-TEST 2023.2 project and package reports can be displayed in the locally installed TRF viewer with a simple click from TEST-GUIDE. The TRF Viewer automatically downloads hosted artifacts as soon as they are needed.

With ECU-TEST 2023.3 this function has been improved even further. Artifacts referenced by project reports are now reliably identified and loaded by TEST-GUIDE.

Downloaded reports and artifacts are stored in a subfolder of the temp directory. This cache directory is now automatically cleaned so that only recently used reports are kept. The corresponding algorithm is configured in the program settings.

Automotive File Exchange now also for bus databases

The option to reference A2L and HEX files via TEST-GUIDE, existing since ECU-TEST 2022.4, is now also possible for bus databases.

For this purpose, the test configuration editor provides the option to search and reference bus description files via the depository browser in the Bus access tab.

Touch input test step

Until now ECU-TEST offered interaction with screen contents only via tool specific job test steps. These are very technical, not transferable and not very intuitive.

The new action Touch input on the Image element in the Media access tab, now allows intuitive input of various actions directly with the screen content in front of your eyes.

Supported Actions
Tap, Hold, Multi-Tap, Swipe, Hold and Swipe, Multi-Swipe, Pinch, Rotate

Note: Currently, the test step is only supported in combination with ADB.

ASAM Capture Module Protocol (CMP) support

For access to bus and Ethernet communication, ECU-TEST now supports the new ASAM CMP standard. The activation of the standard can be done on all logger ports.

Evaluation of RTMaps logging during simulation

We have implemented two new tool jobs to make the RTMaps logging available live in the test case:

StartLogMonitor

StopLogMonitor

These jobs can be used to evaluate the logging in the test case in parallel and also for reacting to it accordingly (e. g. by aborting the test).

New features for the REST-API

Constants submitted are available at the configuration start

In the test configuration and the testbench configuration, global constants can be set via REST API and are available when the configuration is started.

---

Display error message in case of failed report upload

Previously, error messages were only displayed in the ECU-TEST log file. The error message that currently appears in the log is now also sent back via the REST API endpoint.

Example: "Auth failed", "Report already uploaded", "..."

Enum variables revision

The package variables of type Enum have been revised. In the test case and in the trace analysis, an Enum value is now used instead of the Int value. This supports the flexible comparison with number and text. The representations are accessible via myVar.int and myVar.str.

Using myVar.enum – supported by auto-completion – you can access specific values of the defined enumeration, so that sustainable comparisons can be realized.

Analysis packages from library workspaces

Analysis packages from library workspaces are now displayed in the Workspace tab and can be used in the project.

Note: In the next release, the use in trace analyses will also be supported.

Visualization of individually calculated signals in the plot

Individually calculated signals can be defined for a plot. This makes it now much easier to plot specific elements of an array or attributes of an object-valued signal, such as SOME/IP messages.

It is also possible to calculate with one or more signals or to specify a constant value.
The identifier for the legend can be assigned independently of the formula.

Expansion of the If-Then-Else block

An If-Then-Else block has been added in ECU-TEST 2023.2 to the trace analysis. This supports more flexible variant handling and a more dynamic analysis process by executing trace steps or entire episodes depending on package variables.

With ECU-TEST 2023.3 two new functions are available in the If condition:

SampleCount(signal)

IsFound(signal)

These are most useful when checking for the presence of optional trace analysis signals.

AutoSPY: Import of bus loggings and search for signal conditions

If additional signal data is required for understanding or evaluating a trace analysis, it can be subsequently imported into an existing AutoSPY document. While AutoSPY Analyzer only supported MDF4 and CSV files so far, it now also allows the import of additional signals from bus logging files of type ASC, BLF and TTL.

If you have too much signal data in an AutoSPY document to view it manually only, the search function in AutoSPY Analyzer helps you to find specific events in the trace quickly and easily.

In addition to numeric and Boolean signals, the search function now also supports text-valued signals whose samples are single characters or strings.

Viewing TEST-GUIDE key indicators in AutoSPY

The KPIs over multiple test case executions can now be viewed not only on the TEST-GUIDE detail page.

Using the new Export AutoSPY button, all key indicators of a test case in the filtered time range can be exported as an *.astrace file.
Then, the results can be viewed and analyzed in more detail in the AutoSPY Viewer or in the AutoSPY Analyzer for ECU-TEST.

Note: This new functionality is also available in the Export view of the report filter.

HashiCorp Vault for HTTPS Authentication

"With Vault, tokens, passwords, certificates, keys and other sensitive data can be stored securely and the access to them can be strictly controlled."

Access data for third-party systems in TEST-GUIDE, e.g. Git and SVN, can now also be provided via the external HashiCorp Vault Secret Manager.

Under Project Settings > Secret Management, a secret management of the type Vault can be configured.
The credentials of the configured Vault can be used to authenticate an SCM configuration over HTTPS.

SFTP storage for artifact management

The TEST-GUIDE artifact management now also supports storages of type SFTP (Secure File Transfer Protocol).

When configuring SFTP storages, you can choose between basic authentication (username and password) and SSH key authentication (username and private SSH key).

After configuring a depository with this type, artifacts can be uploaded there, downloaded and also deleted from there as usual.

E-mail subscription on releases

All information about the current status of a release can be easily accessed by subscribing to a release or a release folder, which is sent as an e-mail.

This includes release-specific information such as the distribution of test results, the number of test executions, the start and end date of the release, or even the link to the release detail view. On this page, you set a subscription by clicking on the Subscribe button.

E-mail subscription on Playbooks

Playbook executions can now be subscribed to. This is useful in case something fails during the highly automated execution.

Notification is sent by e-mail when all execution jobs generated from the playbook have been completed for a playbook run.

In addition to notification of failed, notification of successfully completed playbook executions is also possible.

Navigation links configuration

In the TEST-GUIDE navigation, team links can be added to the project. In this way, all important data can be accessed quickly from TEST-GUIDE.

Add the links under Project Settings > App Links.