Hamcrest to AssertJ dependency tests #390
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
|
Merging now to see if pipeline still passes |
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's changed?
Add tests to verify hamcrest to assertj dependencies are added with correct scope.
What's your motivation?
When running through the platform, I saw Gradle dependencies added where they might not have been needed.
Anything in particular you'd like reviewers to focus on?
Potentially limited value having these here. Should we still add them?
Have you considered any alternatives or workarounds?
Might need to troubleshoot elsewhere, but this is at least a sanity check that dependencies are added with the right scope and only if using.