Split e2e fixtures from anonymized dump
Closed this issue · 2 comments
inyono commented
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
hugotiburtino commented
Add another database (with minimal schema / data) that is intended for automated testing, generated via migrations.
Interesting solution, I will think about it along side with the idea of having just one repo setting up tests for backend
hugotiburtino commented
Actually, we can run now e2e tests against staging, so it is not really a problem anymore.