You might also want to consider the possibilities that you have problems but haven't noticed them yet or that your experience is not a global truth applicable to all projects.

If you think about the problem more, ask yourself how it's possible to mock a remote HTTP call without the risk of this problem? I've seen people write frameworks which periodically save and cache responses but unless you regularly perform some kind of validation there's no way to avoid that problem.