A data model and the related database of course change from time to time. New features are introduced, old and deprecated data types are removed and new relations embedded. Data integrity ensures your application works as it’s supposed to. Consider two different scenarios:
- Another system introduces changes, which affects the API in whatever way. You are able to say for sure, no changes of your own system lead to this error and you can easily take action to solve this issue instead of tracking down the instance which could have been responsible for the error. In theory ;-)
- Some changes lead to side effects and affect other test scenarios. React on them and keep everybody’s daily-business up and running instead of facing a problem several days after a change, when the error finally occurs.
At last: be honest. How many times did you think: „This solution is engraved in stone, my children’s children will still benefit from this“ – and now let’s face reality ;-)