Run unit tests in alphabetical order #246
Merged
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.
https://jira.lyrasis.org/browse/VIVO-2005:
Adds runOrder to unit tests to ensure that they are run in an order that allows all tests to have properly set-up dependencies. This is a temporary workaround for the general problem to be addressed in https://jira.lyrasis.org/browse/VIVO-2003
How should this be tested?
Should be tested with the companion Vitro pull request vivo-project/Vitro#244.
Test that VIVO builds normally and that all the unit tests are run in alphabetical order.
Before merging, change the base branch dropdown to rel-1.12.1-RC (once it becomes available).
Interested parties
@VIVO-project/vivo-committers