Disable Alembic migrations during testing #17
Merged
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
A side-effect of initializing the Alembic database schema migration system is that it creates directories on the file system. This breaks the test suite in some environments and bloats test startup time. Since we don't need Alembic to run our acceptance tests, we replace Alembic with a stub.
|
👍 to merge from @zalun |
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.
A side-effect of initializing the Alembic database schema migration
system is that it creates directories on the file system. This
breaks the test suite in some environments and bloats test startup
time. Since we don't need Alembic to run our acceptance tests, we
replace Alembic with a stub.