Build: split tests that need database from those that do not #12123
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
Update adds a tag to tests that need a database. We then split the build such that 'test' no longer runs these tests, and 'testWithDatabase' does (and we add 'testAll' to test all) This allows for './gradlew test' to no longer depend on any running docker containers & faster game-headed development.
DanVanAtta
force-pushed
the
test-with-database
branch
from
2011b2c to
65e7511
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.
Update adds a tag to tests that need a database. We then split the build such that 'test' no longer runs these tests, and './gradlew testWithDatabase' does.
This allows for './gradlew test' to no longer depend on any running docker containers & faster game-headed development.