TestSessionLabelProviderCustom shows JUnit 5 TestTemplate poorly #19
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.
When org.eclipse.jdt.junit.runners is included in a product, JUnit 5 TestTemplate tests are not displayed correctly in the JUnit view. E.g. a RepeatTest is displayed as follows:
test.TestTemplatesJunit5
** test1
Without this plug-in, the JUnit view has more useful contents:
TestTemplatesJunit5
** repetition 1 of 1
This is due to outdated contents in TestSessionLabelProviderCustom, when compared to TestSessionLabelProvider. Only the latter was updated to deal with JUnit 5 tests.
This change adjusts TestSessionLabelProviderCustom.getSimpleLabel() to the change in TestSessionLabelProvider.getSimpleLabel() for: https://bugs.eclipse.org/bugs/show_bug.cgi?id=488566
Fixes: #18