Allow static imports in tests #240
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
uschi2000
reviewed
Feb 6, 2018
| org.assertj.core.api.Assertions.*, | ||
| org.assertj.guava.api.Assertions.*, | ||
| com.google.common.base.Preconditions.*,com.google.common.truth.Truth.*, | ||
| com.google.common.base.Preconditions.*, |
There was a problem hiding this comment.
nit: can you split 77 into two lines?
uschi2000
approved these changes
Feb 6, 2018
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.
Follow-up to #239
Rationale is that many testing libraries rely on static imports - maintaining an increasingly large list of exceptions just suggests that banning static imports in test code doesn't make sense in the first place.