DRYD-2089: Updates to Integration Tests#534
Merged
mikejritter merged 6 commits intoMay 12, 2026
Merged
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
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.
What does this do?
Why are we doing this? (with JIRA link)
Jira: https://collectionspace.atlassian.net/browse/DRYD-2089
This is the last step of getting the upgrade branch ready for merging back into develop. It makes updates so that all of the tests in the repository will pass. Mostly it's adding dependencies which were dropped likely due to shuffling of things, as well as some more hibernate configuration changes which were expected. Any configuration which isn't being used has been removed as well as having any build.xml/pom.xml references removed.
How should this be tested? Do these changes have associated tests?
mvn testand see that all tests passDependencies for merging? Releasing to production?
This will need full regression testing once we merge into develop.
Has the application documentation been updated for these changes?
No. Build documentation needs to be updated.
Did someone actually run this code to verify it works?
@mikejritter tested locally
Have any new security vulnerabilities been handled?
n/a