You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is possible to build a golang binary with coverage reporting enabled [1]. That will allow the integration tests to run the actual elastic-agent binary and have it report its coverage report. The coverage report should then be copied back to the developer or CI machine.
This would really help provide true coverage of the Elastic Agent repository with both unit and integration tests.
I believe if these reports land in the following folder/files, SonarQube should start picking them up and reporting more accurate stats for code that gets integration-tested but not unit-tested:
It is possible to build a golang binary with coverage reporting enabled [1]. That will allow the integration tests to run the actual
elastic-agent
binary and have it report its coverage report. The coverage report should then be copied back to the developer or CI machine.This would really help provide true coverage of the Elastic Agent repository with both unit and integration tests.
[1] https://go.dev/doc/build-cover
The text was updated successfully, but these errors were encountered: