-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support schema definitions in the database type #110
Comments
This sounds like a good idea, that we'd reduce the database set-up complexity before running tomato. But I have a few questions regarding this approach
resources:
- name: tomato-mysql
type: mysql
params:
datasource: mysql://user:pass@tcp(localhost:3306)/hello
initdb: some-path/dbschema.sql |
I think you raise some good points, I'm not sure if it would make sense in the Gherkin clauses considering the breaking changes. I like the thought of a general init stage for the resource in this case, I could see this even expanding for other resources (e.g wiremock) that have a similar set of procedures for the initializing process. |
Is your feature request related to a problem? Please describe.
Define database schema using Gherkin clauses.
Describe the solution you'd like
Support for sql schema definitions inside the feature test files.
Describe alternatives you've considered
Migrations as part of the database setup/teardown process. Support inside the database resource
The text was updated successfully, but these errors were encountered: