So now we cannot get information about how much code is covered by unit tests and with integration tests? If the coverage by itests is too high, it is possible risk. Integration tests are obviously heavy, complicated, slow, … but on the other side give more real usage results. Having this information is useful even if it is not exact.
Can we expect some changes in this problematic? I have another problem - coverage of application modules produced by integration tests run with TestContainers and Docker is ignored by SonarQube. I can look at it only with the Eclipse editor (I can import the *.exec file and it works).
Also, even SonarQube 7.4 tells the count of Unit tests, but it is count of all JUnit tests.
… a day later, EDIT: I finally managed to merge the exec file produced by the docker run, so my “another problem” is resolved.
If someone would need to help … set the relative path to the additional common exec file in project administration and it’s all, for example:
Sonar will merge all available exec files and filter only classes from the current module.