This repository has been archived by the owner on Apr 14, 2022. It is now read-only.
Added Cobertura task to Gradle. #20
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hi,
I was thinking about two stack overflow bugs I've fixed lately. And I came to conclusion that we could had easily spotted them earlier with test coverage checks. From my experience Cobertura works pretty good as Scala test coverage tool.
Unfortunately in Gradle you cannot use Cobertura out of the box (as in Maven), so I created a dedicated Gradle task to generate Cubertura report.
Now, if you want to generate test coverage report, you just execute
gradle cobertura. After the execution of the latter command, you will see brand new coverage report in HTML format located underspring-scala/build/reports/cobertura/index.html.Keep in mind that I added Maven Central repository to the
build.gradlebecause the Cobertura task needs to resolvenet.sourceforge.cobertura:cobertura:1.9.4.1dependency. If you add mentioned dependency to the Spring Source repository, you can safely remove Maven Central frombuild.gradle.Armed with Cobertura I could improve our test coverage with some further contributions.
Best regards.