Better support for junit5 parameterised tests#687
Merged
Conversation
eroshenkoam
approved these changes
Nov 30, 2021
This was referenced Dec 2, 2021
Closed
Closed
Closed
1 task
1 task
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Context
Allure now detects junit test templates. For test templates test result name is set to concatenation of template's display name and invocation's display name. For example, the following test:
will be displayed as
test(ArgumentType) [1] argumentValue=some valuein the report.This also allows usage of
@DisplayNametogether with@ParameterizedTest(fixes #500):will be displayed as
My named test [1] argumentValue=some valuein the report.Besides that, all the parameters will be displayed correctly as well. Including support for new
@Paramannotation:Checklist