Closed echarrod closed 5 years ago
Hi, has this been resolved? The same behavior is seen from my environment as well.
I haven't been able to get it working on my environment, hoping someone can look at it
hello,
I managed to reproduce the problem. Issue is that go test
is using module name as a package in the json report. We currently don't support modules. I created issue #378 to track it
Thanks @saberduck. Please let us know when the fix is implemented.
Best regards, Edwin
Any progress with this?
@saberduck are there any updates with this?
@em503c this repository will not be updated anymore. New Go plugin for SonarQube is available in this repository https://github.com/SonarSource/slang. I created ticket https://jira.sonarsource.com/browse/SONARSLANG-450 to track this issue.
Please open a thread on our community forum https://community.sonarsource.com/ if there is something else to discuss, this repository will be soon archived.
Description
Sonar scanning seems to not find the test files, but I can't work out why. There is some coverage, so I'm not sure where this is from.
I get
line-rate="0.6259947"
incoverage.xml
, so it looks like that is getting the coverage right, but the sonar report is only showing about half that much.Steps to Reproduce
Content of your sonar-project.properties
Log of sonar-scanner related to the plugin
Test.xml file:
(classname="v2")?
Versions
server: sonarqube-7.7 sonar-scanner: sonar-scanner-cli-3.3.0.1492-windows /
sonarqube
gometalinter: v3.0.0 go: 1.12 GO111MODULE=auto OS Windows 10