Unable to analyse coverage for Golang application on Azure DevOps

[Quentin (Quentin Jaquier)]

Hello @benhdev

I invite you to have a look there:

Sonar scanner fails to load Go test results

SCM: github.com CI: travis Scanner: travis addon sonar scanner Language: go 1.13.x sonar-project.properties sonar.projectKey=my-project-key sonar.projectName=my-project-name sonar.exclusions=**/*_test.go,**/*_generated*.go,**/*_generated/**,**/vendor/** sonar.test.inclusions=**/*_test.go sonar.test.exclusions=**/*_generated*.go,**/*_generated/**,**/vendor/** sonar.go.tests.reportPaths=report.json sonar.go.coverage.reportPaths=coverage.out Snippet from .travis.yml - stage: sonar …

And there for a nice 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.…

Hope it will lead you in your research.

Best,
Quentin