Move assert methods from ResourceTest to dedicated utility class #903 #904
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
This was referenced Nov 30, 2023
HeikoKlare
force-pushed
the
ResourceTest-extract-utils-assert
branch
from
bdbec07 to
efd8a26
Compare
…pse-platform#903 This changes moves all assert* utility methods defined in ResourceTest to a dedicated ResourceTestUtil test class. It prepares for removing the JUnit 3 test inheritances hierarchy to migrate to JUnit 4. Contributes to eclipse-platform#903
HeikoKlare
force-pushed
the
ResourceTest-extract-utils-assert
branch
from
efd8a26 to
cd4f867
Compare
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.
This changes moves all assert* utility methods defined in ResourceTest to a dedicated ResourceTestUtil test class. It prepares for removing the JUnit 3 test inheritances hierarchy to migrate to JUnit 4.
Contributes to #903