Refactored persistence integration tests not to require Glassfish #2618
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
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.
The proposal is to remove the necessity of running Glassfish to run integration tests. By manually instantiating EntityManager, integration tests are run just like ordinary JUnit tests. This also speeds up test suite execution.
The intention is to refactor integration tests in dataverse-webapp to use this solution and not require Glassfish at all.
I am aware that this does not mimic she Glassfish runtime (transactions not present), and some rare bugs might not be detected, but I think that having a fast, sefl-contained test suite that can be run more frequently offsets this.