We've had discussions about this at work. New versions of our service got deployed once per week, barring delays and hotfixes. Sometimes we'd miss a release, a

We've had discussions about this at work. New versions of our service got deployed once per week, barring delays and hotfixes. Sometimes we'd miss a release, and a version would stay in production for two weeks. Maybe there would be a code freeze and we'd miss a release, and a version would stay in production for three weeks. We occasionally saw problems. Some cache would fill up over two weeks but wouldn't empty, or something like that. Something that you'd like to test, but which doesn't show up unless you run something in production for a month. I advocated a simple solution: either check that the process runs for multiple weeks in testing, or restart the process every week in production. In other words, don't test it in production.