test: migrate AccessTest to Junit 5 #4438
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
The following has changed in the code: Replaced junit 4 test annotation with junit 5 test annotation in testCanVisitVariableAccessAndSubClasses Replaced junit 4 test annotation with junit 5 test annotation in testCanVisitFieldAccessAndSubClasses Replaced junit 4 test annotation with junit 5 test annotation in testCanVisitArrayAccessAndSubClasses Replaced junit 4 test annotation with junit 5 test annotation in testStackedAssignments Replaced junit 4 test annotation with junit 5 test annotation in testRHS Replaced junit 4 test annotation with junit 5 test annotation in testFieldWriteDeclaredInTheSuperclass Replaced junit 4 test annotation with junit 5 test annotation in testVariableAccessInNoClasspath Replaced junit 4 test annotation with junit 5 test annotation in testAccessToStringOnPostIncrement Transformed junit4 assert to junit 5 assertion in testCanVisitVariableAccessAndSubClasses Transformed junit4 assert to junit 5 assertion in testCanVisitFieldAccessAndSubClasses Transformed junit4 assert to junit 5 assertion in testCanVisitArrayAccessAndSubClasses Transformed junit4 assert to junit 5 assertion in testStackedAssignments Transformed junit4 assert to junit 5 assertion in testRHS Transformed junit4 assert to junit 5 assertion in testVariableAccessInNoClasspath Transformed junit4 assert to junit 5 assertion in testAccessToStringOnPostIncrement
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.
#3919
The following has changed in the code:
Replaced junit 4 test annotation with junit 5 test annotation in testCanVisitVariableAccessAndSubClasses
Replaced junit 4 test annotation with junit 5 test annotation in testCanVisitFieldAccessAndSubClasses
Replaced junit 4 test annotation with junit 5 test annotation in testCanVisitArrayAccessAndSubClasses
Replaced junit 4 test annotation with junit 5 test annotation in testStackedAssignments
Replaced junit 4 test annotation with junit 5 test annotation in testRHS
Replaced junit 4 test annotation with junit 5 test annotation in testFieldWriteDeclaredInTheSuperclass
Replaced junit 4 test annotation with junit 5 test annotation in testVariableAccessInNoClasspath
Replaced junit 4 test annotation with junit 5 test annotation in testAccessToStringOnPostIncrement
Transformed junit4 assert to junit 5 assertion in testCanVisitVariableAccessAndSubClasses
Transformed junit4 assert to junit 5 assertion in testCanVisitFieldAccessAndSubClasses
Transformed junit4 assert to junit 5 assertion in testCanVisitArrayAccessAndSubClasses
Transformed junit4 assert to junit 5 assertion in testStackedAssignments
Transformed junit4 assert to junit 5 assertion in testRHS
Transformed junit4 assert to junit 5 assertion in testVariableAccessInNoClasspath
Transformed junit4 assert to junit 5 assertion in testAccessToStringOnPostIncrement