-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
plans to include code coverage & test results reports ? #9
Comments
It has not been planned yet. If you provide an example of the outputs you want to consume by the plugin I can add it. It should be easy. |
OK, I will try and look into this sometime this week. |
Hi. @kmoco2am I'm generating coverage with the command "cov <- covr :: azure (quiet = FALSE)" and testing with "rcmdcheck :: rcmdcheck (args = '--no-manual', error_on = 'warning', check_dir = 'check' ) ". I have attached the generated files and the format, as it would be possible to add these results to the sonarqube analysis. Thanks for any help and I stay tuned. file: coverage.xml
file: test-results.xml
|
So finally I have found some time to look at this. I am sorry for delay. I found out that SonarQube is able to consume "generic" coverage data: https://docs.sonarqube.org/latest/analysis/generic-test/ And covr is able to generate that format easily:
Then it is necessary to add configuration for SonarQube scanner:
It works nicely if there are "modules" but it does not work for my sample project because R code generates XML with file paths containing "module" name at the beginning and it cannot be turned off. Is it the same case for you? Could you try it? |
So, I have added code coverage into sample project. I had to add a piece of R code to remove module name which is included by I am not sure if it is the right solution but it can be used as a workaround until there is valid fix. |
Hello,
Are there any plans to extend this plugin to accept R covr coverage reports, and or unit test results reports in the generic sonarqube xml format?
This would add a lot of value to this plugin.
The text was updated successfully, but these errors were encountered: