Add a separate testing configuration #44
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
This separates the testing configuration into a different docker-compose file that extends the base file. This specifically mounts the bin directory and more importantly assigns a 'testing' database separate from the base database, 'repository'. This allows one to have a functional database that maintains its data regardless of test runs. Previously, we would wipe the database before a test run.
Codecov Report
@@ Coverage Diff @@
## master #44 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 14 14
Lines 277 277
=====================================
Hits 277 277 |
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.
This separates the testing configuration into a different docker-compose
file that extends the base file. This specifically mounts the bin directory
and more importantly assigns a 'testing' database separate from the base
database, 'repository'.
This allows one to have a functional database that maintains its data
regardless of test runs. Previously, we would wipe the database before
a test run.
Closes #34