Issue
In order to always achieve optimum performance in the project while keeping operating costs low, it is important to pay attention to which data is imported into test.guide in the first place. Unnecessary data that is not required in test.guide only costs performance and storage space and therefore money.
Since 80% of the data are 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.
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.
The easiest way is to manage the ATX generator settings centrally via test.guide, then the adjustments can be set directly for the entire project: Project settings > ecu.test
To do this the option must be activated both in the test.guide project
and in the ecu.test workspace
If you work with playbooks and the execution distribution, you must always use this option, as the execution distribution always uses it!
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 the option since version 1.171.0 to define which attributes or constants are recorded in test.guide via the upload rules (Project settings > Upload rules). All others are discarded.
Retroactively remove unused attributes and constants
If all upload settings have been made and you now realize during the analysis that there are many unused attributes/ constants in your project that can be permanently deleted, this is possible using the recycle bin (Project settings > Recycle bin) function.
If you discover within a few days after deletion that certain attributes or constants for filtering/analysis are still missing, these can be restored as long as the recycle bin has not yet been emptied.
The attributes and constants are also permanently removed from locked releases!
In order to prevent mass deletions from affecting ongoing operations, only one deletion action can be carried out in the project at a time.
Define cleanup rules
If, for example, 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 required.
This has the advantage that only the results relevant to the delivery remain available via the locked releases and no unnecessary data is kept in the project for longer.