Once you’ve scanned your main branch, you should be able to see the Code tab (including all files analyzed, which this “estimated after merge” figure represents) and understand what files are being included in this figure.
I think this will help you understand what could be the source of the discrepancy. For example – SonarCloud includes all files in the coverage calculation that have “executable lines” – not just the ones included in a coverage report. If you have a mixed-language project, that could be the source.
Noted, i thought the code coverage value is from the coverage.xml, but that is not the case.
How could i make SonarCloud to only calculate Coverage in folder /src & /service, and i still want sonar to scan all file & directory but exclude the coverage. - Is this possible ?
The Analysis Scope documentation should help you understand how you can exclude certain files from coverage (unfortunately, only exclusions are possible, not inclusions)
