Final fix for coverage

[bobismijnnaam]

There was a bug that caused the coverage reports not to be merged correctly in the action, causing sonarcloud to display 0% coverage.

[sonarcloud]

SonarCloud Quality Gate failed.

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

0.0% Coverage
0.0% Duplication

[bobismijnnaam]

I think the coverage code smell can be ignored, as it concerns coverage in the test suite code, and it requires changing the CI to get the coverage there, so I don't think it's worth the effort.

[Vescatur]

I think the coverage code smell can be ignored, as it concerns coverage in the test suite code, and it requires changing the CI to get the coverage there, so I don't think it's worth the effort.

I am questioning the usability of the rule for us. Since most of the project is not covered by tests it will give a lot of warnings.

[bobismijnnaam]

Since most of the project is not covered by tests it will give a lot of warnings.

We'll have to see I guess. We can also turn off the coverage for certain classes/packages, I think, that might help.