Add Junit5-params dependency for projects without it when needed #620 #829
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.
Description
Now libraries are configured properly when generating parametrized tests with Junit 5:
junit
libraries as dependency, check forjunit-jupiter
orjunit-jupiter-params
libraries and if neither of them is installed, installjunit-jupiter-params
junit
libraries, installjunit-jupiter
(behavior in this case is the same as before PR)Fixes #620
Type of Change
How Has This Been Tested?
Manual Scenario
Scenarios on which behavior was checked:
junit-jupiter-api
andjunit-jupiter-engine
dependency --junit-jupiter-params
dependency is addedjunit-jupiter
dependency -- nothing addedjunit-jupiter
dependency is addedChecklist (remove irrelevant options):
This is the author self-check list