- Notifications
You must be signed in to change notification settings - Fork45
assertArrayEquals overload is not found, tests doesn't compile #135#464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Vassiliy-Kudryashov merged 1 commit intomainfromVassiliy-Kudryashov/135-assertarrayequals-overload-is-not-found-tests-doesnt-compileJul 11, 2022
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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
EgorkaKulikov approved these changesJul 11, 2022
resolving merge conflict with main branch, use the very last (just added to the list) library with matching name
3d5c582 to94c695aCompareSign up for freeto 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.
Description
JUnit 4.12 is minimal required version for API compatibility reasons.
We detect precise version via library name and its JAR names as fallback.
In case user have JUnit 4.11 or older in project configuration "our" JUnit from Maven should be put in library listupper than old one to provide proper imports in tests
Fixes#135
Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
Manual Scenario
Add JUnit 4.11 or older in project dependency
Generate tests for examples.PrimitiveArrays, resulting code uses assertArrayEquals(boolean[], boolean[]) that is absent in JUnit 4.11 or older, code won't compile. At first stage of generation JUnit 4.13.2 should be installed and puthigher than existing 4.11. As result test code can be compiled successfully.
Checklist (remove irrelevant options):