SonarCloud code coverage % for GoTest files using Bitbucket Pipeline

[sanjay_a (Sanjay Ashok Kumar)]

Hi community,

I’m looking for an help that I’m unable to get the code coverage % in Sonar Cloud for Go Test Files(main_test.go) using the below Bitbucket pipeline script.
Script to Run Go Test

• cd src/workspace
• go build -v -o workspace
• go test -v -short -coverprofile workspace_coverage.out ./…
• go tool cover -func=“workspace_coverage.out”

Below is the result of go tool command

Bitbucket Sonar Successfull Result

Script:

• pipe: sonarsource/sonarcloud-scan:1.2.1
  variables:
  SONAR_TOKEN: ${SONAR_TOKEN}
  EXTRA_ARGS: ‘-X -Dsonar.sources=. -Dsonar.c.file.suffixes=- -Dsonar.cpp.file.suffixes=- -Dsonar.objc.file.suffixes=- -Dsonar.test=src/workspace/_test.go -Dsonar.test.inclusions=src/workspace/_test.go -Dsonar.go.coverage.reportPaths=src/workspace/workspace_coverage.out’

Code Coverage details in Sonar Cloud

Overview of Code Coverage

When i cross check with bitbucket pipeline artifact for sonar scanner it throws an warning message as below.
19:17:34.236 DEBUG: Resolving file workspace/main.go using relative path
19:17:34.237 WARN: File ‘workspace/main.go’ is not included in the project, ignoring coverage

Will be waiting for your response.

Thanks,
Sanjay A

[sanjay_a (Sanjay Ashok Kumar)]

Hi Community,

Can anyone help me out with the answer for the above problem.

Thanks,
Sanjay A

[Quentin (Quentin Jaquier)]

Hello @sanjay_a

I know it’s an old topic, but I was wondering if you managed to solve your problem? If yes, it would be great if you could share with us what was the problem.

If not, I invite you to have a look at this example of how someone configured his project.

SonarGo code coverage 0%

For anyone else who may find it helpful, now that my build process is working, here is a simplified run down of my settings and build process: My first step is to run my tests and generate my a coverage report and test report: go test "./..." -coverprofile="coverage.out" -covermode=count -json > report.json; I also added an optional step to generate a go linter report using this 3rd party cli golangci-lint run ./... --verbose --no-config --out-format checkstyle > golangci-lint.out My sonar.…

And eventually at this related post:

Sonar scanner fails to load Go test results

So I figured it out. The secret was in Cameron’s properties file, but it’s not clear what it is. When I ran with just this (omitting projectKey and projectName): sonar.go.tests.reportPaths=report.json sonar.go.coverage.reportPaths=coverage.out I got code coverage, but not test results. So my assumption was that the default values for sonar.sources and sonar.tests was correct and the issue was in how tests were processed. This assumption turned out to be wrong (as they generally are). I clone…

Hope it will lead you in your researches.
If you are still stuck, feel free to come back to us with updated information.

Best,
Quentin