This is part of the integrations package setup (integration tests with fixtures): We have some sensitive data in the production db (names, emails, etc...) which shouldn't be made public (committed to the repo as fixtures). However, we would still like to be able to use the the production data (as fixtures) to perform tests on. To mitigate this, I suggest we create a script that maps the names, surnames, emails, etc... from the production generated json backup and replaces each occurrence with some dummy data, making the fixtures safe to commit to a public repo.
ikusteu
commented
9 months ago
This is part of the integrations package setup (integration tests with fixtures): We have some sensitive data in the production db (names, emails, etc...) which shouldn't be made public (committed to the repo as fixtures). However, we would still like to be able to use the the production data (as fixtures) to perform tests on. To mitigate this, I suggest we create a script that maps the names, surnames, emails, etc... from the production generated json backup and replaces each occurrence with some dummy data, making the fixtures safe to commit to a public repo.