Feature/WEOS 1298 - Ensure end to end tests run against all supported databases #94
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
got mysql database to clear on reset step
Weos 1300
added flags for running end to end on mysql and postgres
feature: Weos 1301 Run BDD test using Mysql and Postgres
Bug:Weos 1331 - Fixed issue where indexes were not being added properly to postgres database
let foreign keys for many to many relationships be autogenerated to mitigate against errors updated delete content feature file to have injectable database configurations
feature:Weos 1330 - MySQL migration bug fix
atoniaw
changed the title
WEOS-1301 added additional projections tests
akeemphilbert
previously approved these changes
Feb 14, 2022
ensured events were being pulled from db in ascending order
foreign key configured in main_test file
akeemphilbert
approved these changes
Feb 16, 2022
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 kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: