...
| Table of Contents | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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.
...
| Note |
|---|
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 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).
...
| Info |
|---|
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
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.
...