Issue

In order to achieve optimal project performance while keeping operating costs low, it is important to consider what data is imported into test.guide in the first place. Unnecessary data that is not needed in test.guide only costs performance and storage space, and therefore money.

Since 80% of the data is usually attributes and constants, the focus is on optimizing them. Methods for optimizing data handling are presented below.

Solution

Quick analysis of the current stored constants and attributes

To get a quick overview of which attributes or constants are used in the project, it is sufficient to search for the constant/attribute key in the result filter using the * operator. If many values appear here that are not desired for the search in the test.guide, it is advisable to suppress their import.

Open

Open

Specify which constants and attributes are to be uploaded to test.guide

Client side

In ecu.test coveredAttributes and coveredConstants in the ATX generator settings can be used to define which values are recorded for the ATX export and are therefore also available for filtering and display in test.guide.

To do this the option must be activated both in the test.guide project

and in the ecu.test workspace

test.guide project settings

If you have no influence on the ATX export, e.g. because it is provided by other teams, test.guide offers since version 1.171.0 the possibility to define via the upload rules (Project settings > Upload rules) which attributes or constants are recorded in test.guide. All others will be discarded.

Retroactively remove unused attributes and constants

If all upload settings have been made and you realize during the analysis that there are many unused attributes/constants in your project, you can permanently delete them using the recycle bin function (Project settings > Recycle bin).

If you discover within a few days after deletion that certain attributes or constants are still missing for filtering/analysis, they can be restored as long as the recycle bin has not been emptied.

Define cleanup rules

For example, if the current test runs / integrations / trials have been completed and the important results are locked as a release, it is beneficial to directly define a cleanup rule that automatically removes all data from test.guide that is no longer needed.