You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 3, 2024. It is now read-only.
We shoud probably split the fixtures intended for testing from the dump for a couple of reasons:
We can't update the anonymized dump easily
We can't run the e2e tests in staging (since they don't have that stuff)
It's hard to update the test data
To achieve this, we should IMHO:
Add another database (with minimal schema / data) that is intended for automated testing, generated via migrations. This way, the anonymized dump can be exchanged / kept up to date. And the testing database can be rolled back whenever (maybe even similar to django after every test), should also be easily applicable to staging / production deployments
The text was updated successfully, but these errors were encountered:
We shoud probably split the fixtures intended for testing from the dump for a couple of reasons:
To achieve this, we should IMHO:
The text was updated successfully, but these errors were encountered: