Implement auto-configuration for code-coverage in Gradle #5399
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What Does This Do
Adds automatic configuration of per-test code coverage for Gradle projects.
If
dd.civisibility.jacoco.plugin.version
property is provided when running a Gradle build with the tracer attached, the tracer will automatically configure Jacoco plugin of the given version to be used with the build.Motivation
In order for the tracer's per-test code coverage feature to work, Jacoco needs to be used in the project.
The usual way of enabling Jacoco would be to update a Gradle build file, registering Jacoco plugin and adding a Jacoco task.
The clients often have troubles doing this, and are in general reluctant to modify their build files.