Set up JaCoCo Code Coverage, update Gradle wrapper#756
Conversation
|
Currently this creates separete coverage reports. I am experimenting to ultimately have one single report generated for all projects |
littleaj
left a comment
There was a problem hiding this comment.
I want to explore options other than using common-java.gradle for add the code coverage
|
@littleaj tried to play around a bit after you left, seems like xml is not getting generated somehow by moving to the subprojects. Also it's not picking the specified version of Jacoco. I think that subprojects closure is not being used at all. Its just picking up the default configuration of jacoco. We might for now just keep it into commons-java file and later experiment. |
…va.gradle" This reverts commit a9301b4.
|
@littleaj as mentioned, in the comment above, I have reverted your commit to ensure that xml's are being generated. I think we can be satisfied with this for now and later on move experiment more for combined report. Let me know your thoughts. |
|
That makes sense. I guess we'll use the import file for now. |
This PR sets up JaCoCo code coverage, updates Gradle wrapper to 4.2 (updating beyond this fails native linking), fixes build.gradle file for web module and cleans some imports in tests.