Skip to content
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

Databases reset feature for testing #5

Open
AymDev opened this issue Jun 24, 2020 · 0 comments
Open

Databases reset feature for testing #5

AymDev opened this issue Jun 24, 2020 · 0 comments
Labels
feature Requested or planned feature.

Comments

@AymDev
Copy link
Owner

AymDev commented Jun 24, 2020

Testing the migration requires manually resetting the target database to delete migrated data.

Solution:
Especially if #4 is implemented, target connections databases could reset themselves in development, if a SQL script is provided.

UPDATE 2021-05-17:
Tests using a database can extend AbstractDbalTestCase. It still resets manually.
A test has been made to use an in-memory SQLite database but the DBAL platform does not support foreign key constraints and is incompatible with the foreign key feature as mentionned in ForeignKeyBeforeTask.

Leaving open until doctrine/dbal#4288 is fixed

@AymDev AymDev added the feature Requested or planned feature. label Jun 24, 2020
@AymDev AymDev mentioned this issue May 17, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Requested or planned feature.
Projects
None yet
Development

No branches or pull requests

1 participant