We are working on version 1 of a project , we face challenges when due to some code or schema changes old objects in the database (mongo db) show erroneous behavior.
Current thoughts:
- Create some objects now , preserve their IDs in some config file and from now on treat them as legacy data and write test scripts to validate their behavior, so due to anything their behavior alters it will be caught in test execution.
Problem with this approach
-
The cost of maintainability of these IDs looks higher than what we are achieving with them.
-
Our test scripts relies on the hope that in the course of time these objects will not be modified by anyone else (knowingly unknowingly), as it will be sitting right there in the common database visible to everyone (human/program), so if any validation fails, we always have to check if that was due to bug in the new code or due to some manual changes in test objects / database.
So any thoughts what can be a better approach to achieve this
Aucun commentaire:
Enregistrer un commentaire