(main) Handle mojos default value in tests #756
Merged
Conversation
This file contains 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
abelsromero
changed the title
abelsromero
force-pushed
the
branch-main/issue-609-handle-mojos-default-value-in-tests
branch
from
3bf0cd4
to
e3b7d4b
Compare
abelsromero
force-pushed
the
branch-main/issue-609-handle-mojos-default-value-in-tests
branch
from
e3b7d4b
to
d3fa92f
Compare
abelsromero
deleted the
branch-main/issue-609-handle-mojos-default-value-in-tests
branch
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.
What kind of change does this PR introduce? (check at least one)
What is the goal of this pull request?
Prevent regressions by ensuring unit tests take the
@Parameterconfiguration when mocking Mojos.In fact, an issue in ZipMojo was found.
Are there any alternative ways to implement this?
It's mostly a refactor, so yes...The change also extracts logic from TestUtils to better re-use or even publish as an extra artifact for other maven plugin developers.
Are there any implications of this pull request? Anything a user must know?
no
Is it related to an existing issue?
Finally, please add a corresponding entry to CHANGELOG.adoc