Improve PR coverage wording when no new testable code exists

[adamkwhite (Adam White)]

“Not computed” doesn’t explain why coverage wasn’t computed. The message is ambiguous: it could mean the PR contains no new executable code, or that coverage analysis/import failed because of a misconfiguration.

When a PR contains only configuration changes, please consider displaying “No new executable code to cover” or “Coverage not applicable to this PR,” while retaining the estimated-after-merge value.

References

• Problem with No coverage on Sonaqube Console - SonarQube Server / Community Build - Sonar Community
• ‘Generic Coverage Report’ skipped because of missing configuration requirements. Accessed configurat - SonarQube Server / Community Build - Sonar Community

[andres (Andrés García Solares)]

Hello @adamkwhite, are you on SonarQube Cloud or Server? I noticed the sonarqube-cloud tag on this post, but on SonarQube Cloud this is already implemented: upon missing/0% coverage, a more detailed message is shown, and not a simple “Not computed”.