[
https://issues.apache.org/jira/browse/RATIS-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17283587#comment-17283587
]
Roni Juntunen commented on RATIS-1314:
--------------------------------------
I can try to implement this. I have already some preliminary testing
[here|https://github.com/softgitron/incubator-ratis/commit/d8da9c8d3e440613aef79cc4fa8da96d652b4c6a]
on my fork, but there is still some improvements and testing to be made before
I create pull request. It would be good if RATIS-1311 would be solved before
merging/closing this issue.
> Add JaCoCo coverity tests to Github actions
> -------------------------------------------
>
> Key: RATIS-1314
> URL: https://issues.apache.org/jira/browse/RATIS-1314
> Project: Ratis
> Issue Type: Task
> Components: build
> Reporter: Roni Juntunen
> Priority: Minor
> Original Estimate: 10h
> Remaining Estimate: 10h
>
> Ratis uses currently Sonar for checking general issues and code smells during
> CI run. In addition to static analysis Sonar could be also used for tracking
> coverity of the unit tests. Coverity reports are useful for making sure that
> software is properly tested and amount of test cases is sufficient on new
> features.
> What should be done:
> # Add support for JaCoCo coverage runs
> # Fix or skip test cases that do not work with coverage
> # Make sure that coverage results are sensible
> # Add coverage step to CI pipeline and upload results to Sonar
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
