-
Notifications
You must be signed in to change notification settings - Fork 10
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
WIP: [HELP needed] first attempt based on sonar-puppet module to parse generic-test-data #277
base: master
Are you sure you want to change the base?
Conversation
I thought most people were using the generic test coverage plugin for this? |
that plugin is removed in the 6.7.1LTS version .... |
Yeah I seen the plugin was removed as is now part of core: https://docs.sonarqube.org/display/SONAR/Generic+Test+Data (i haven't tested it however) so are you saying when you pass in test reports sonar.testExecutionReportPaths it's not picked up? |
from the logs ...
|
Can you share the demo project so I can reproduce the issue please? |
Have to remove company specific dependencies first .. I used the most crapy module to introduce puppet testing :) Will setup a quick demo ....
|
@iwarapter demo project : |
posted in the sonarqube mailing list : https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/sonarqube/hON5Z4dfWIA/Cf7yT_zuAwAJ |
One of the reasons coverage is not parsed is due to the different languages puppet uses to wirite tests, namely _spec.rb files. Sonar is not able to map the tests files against the corresponding pp file. |
Just trying to make this plugin parse generic-test-date. Just copied the relevant files from sonar-puppet, but since I'm a noob with java/groovy I'm stcuk ....
I guessed building is done executing ./gradlew build ...
But always get error which I dont find a way to solve them
Maybe I'm just messing everything up ..... so any guidance is very welcome.