Make reports of Junit5 unit tests in @Nested inner classes show up in scan #2638
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the Problem mentioned here: https://community.sonarsource.com/t/number-of-unit-tests-is-not-measured-with-nested-junit-5-tests/4255/3
I added a fix so that testcases in inner class reports are new igored if they where already present in the parent class without completely ignoring test reports from inner classes.
This is neccessary due to the fact that the reports created by the gradle junit5 test runner creates seperate reports for @nested inner class test cases.
As the name property in UnitTestResult seems to be only ever empty in the unit tests i added a default test name (as UUID) to be able to identify all UnitTestResults by name properly.