Today I'm not coming with a post but rather with a question on an interesting topic: Testing in production. Is that something you'll do? What are the tradeoffs?
Short story:
This week I worked on releasing a new App interacting with data form existing services.
The App was having some issues and I wanted to debug locally to fix them, whereas other person insisted to deploy and test in production then fix.
We needed to submit the App to AppStore and PlayStore and his argument was to speed up the review process, mine was that fixing it locally would be cheaper, then we would submit and App that we knew was working.
Any experiences on the topic? What would you have done? What would be your take?
Happy debate and thanks for sharing your ideas. :)
Latest comments (1)
I think having a "prod-like" environment to test issues could be good. Often times testing in production is a really bad idea aside from just the usual stuff around breaking stuff for users (you can use things like special groups and flags to obviate that). There can be other issues like having unaudited access to user data.
The real reason to test in prod most times is to test things at scale. Having large corpuses of test data can help with this in your "prod-like" environments.