Issue

Considerations

Upload: Single ecu.test reports may reach GB in size. Following test execution, a significant amount of time is required to convert test.guide reports to ATX. How can the process be accelerated?
Network: The bandwidth from the test bench to test.guide is occasionally limited. How can the transmission be improved?
Storage: test.guide storage capacity fills considerably in a short period of time following upload of GB-sized reports with attachments. What options do I have?

Solution

1 Upload
2 Network
3 Storage

Upload

There are three options:

You can configure ecu.test so that only certain FAILED/ERROR blocks, for example, are documented in the report. This naturally ensures that the report remains smaller in PASSED steps and that only the fault cases are included.

The ATX generator offers a range of options for customising the generation process. It is essential to set which data should be included.
For ecu.test project runs the new project report (.prf) generates many smaller test reports (.trf) instead of one large file as before. This ensures faster processing and analysis. Therefore, ensure that the new project report format is used in ecu.test.

Network

If the bandwidth for transferring the report from the test bench to test.guide is the limiting factor, it may help to set the ATX option compressUpload. However, this will increase the generation time on the test bench and also increase the time and CPU load required for unpacking on the test.guide side.
Alternatively, it would be better to check which data needs to be uploaded to test.guide for analysis. This can be set in the ATX generator in ecu.test (see above).

Storage

When uploading, test.guide makes a fundamental distinction between database storage and attachment storage.

All traces, images, and videos are considered attachments and are stored in a file repository (e.g., S3 Object Storage or SMB/NAS share).

The metadata for quick analysis of test case executions is obtained from the ecu.test TRF report and stored in the test.guide database. As a rule of thumb, approximately 25% of the TRF size is required for database storage.

For both types of storage, there are remove rules to continuously remove data that is no longer needed for analysis:

With the auto remove rules for file storage, only the selected attachments are deleted and the test case executions remain in test.guide.
With the help of cleanup rules, entire reports can be deleted from the database, including their attachments. It is important to note that reports assigned to a locked release cannot be deleted. However, this can also be automated using report remove rules.