# Unable to provide sonarqube test coverage for go **URL:** \ **Category:** SonarQube Server / Community Build\ **Tags:** go, scanner, coverage\ **Created:** [February 15, 2022, 11:57am UTC](https://community.sonarsource.com/t/unable-to-provide-sonarqube-test-coverage-for-go/58336 "2022-02-15T11:57:20Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Dhanashri\_Palodkar](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/dhanashri_palodkar/32/30413_2.png) [@Dhanashri\_Palodkar](https://community.sonarsource.com/u/Dhanashri_Palodkar)\ **Post date:** [February 15, 2022, 11:57am UTC](https://community.sonarsource.com/t/unable-to-provide-sonarqube-test-coverage-for-go/58336/1 "2022-02-15T11:57:20Z")
Must-share information (formatted with [Markdown](https://commonmark.org/help/)): - which versions are you using (SonarQube=9.3, g0 = 1.17.7) - what are you trying to achieve - we are trying to scan tests in golang code. We have automated template to add sonar scanning. It’s not getting the go tests getting scanned. - what have you tried so far to achieve this After adding **sonar-project.properties** with line stating `sonar.go.coverage.reportPaths=/coverage.out`, we are still not able to get complete coverage for sonar scan. I would like to know how sonar scanning worked for other go user and what can be added in order to get it scanned ---
**Author:** ![ganncamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ganncamp/32/1261_2.png) [@ganncamp](https://community.sonarsource.com/u/ganncamp)\ **Post date:** [February 15, 2022, 5:50pm UTC](https://community.sonarsource.com/t/unable-to-provide-sonarqube-test-coverage-for-go/58336/2 "2022-02-15T17:50:50Z")
Hi, Welcome to the community! Is `coverage.out` located in the directory analysis starts from? Because the path you’ve provided indicates it’s located in the server root. Can you try removing that initial `/`?   Ann