Tests are about expectations - not "realness" of data
A coworker updates the service with another user
The code change was in the wrong service
A new founding member was added to the team (a change in requirements)
This is why developers often refer to test cases and their expectations for how our code should behave as documentation, or a design aid, for their actual code.