Full disclose I don’t use travis and I’m not sure why you’re seeing those warnings about missing test files, but I have been fighting with getting Go coverage and test reports into Sonar for a few days now and finally have it working, so here is a link to the rundown of my build-test process and settings. My inclusions and exclusions are a bit different from yours and I recall seeing some posts about how sonar scanner uses the exclusions and test.exclusions that can result in some behavior that is not intuitive from the property names. Take a look at and maybe emulate my config below and see if that helps?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Can't get tests report | 2 | 1319 | July 15, 2020 | |
| SonarGo not able to follow path to test results | 1 | 1449 | June 25, 2019 | |
| All my .go files are reported to be "excluded for coverage" | 9 | 4940 | July 3, 2020 | |
| SonarGo code coverage 0% | 9 | 14999 | December 4, 2022 | |
| SonarGo not showing unit test results | 5 | 4614 | April 28, 2020 |