It doesn't mean that you discover if something works when it's live and in use. You should test that it does what it's supposed to do before making it publicly available. (It's not an excuse for not verifying your work before saying it's done.)
It doesn't mean that you first lean about any problems with a change when it's in production. Changes should be reviewed before release and possible or likely problems addressed in advance.
It can mean that you release new functionality behind feature flags and roll them out slowly to all people.
It can mean that you A/B test new functionality in real scenarios.
It can mean that you monitor your systems in production to ensure reliability and performance.
It means that you need a way to gather feedback and errors from live systems.
It is also to recognize that things may happen in production that may not happen elsewhere.
Everyone should test in production. No one should only test in production.
0 comments:
Post a Comment
I get a lot of comment spam :( - moderation may take a while.