Yes, you should test on production…
<p>We can define “shipping confidence” as the feeling a mentally sane developer has when they know their code is about to be deployed to production (whether it can be updated over the air or not). Like with any feeling, shipping confidence is a spectrum.</p>
<p>A company can be placed on such spectrum as shown in this example:</p>
<p><img alt="Shipping confidence spectrum. Companies like SpaceX are forced to test the crap out of their software, companies like GitHub allow anyone to deploy straight to prod, see what happens (sometimes employing canary deployments) and rolling back if required. People like levels.io deploy to prod and use their customers to test. These are all good strategies." src="https://miro.medium.com/v2/resize:fit:1000/1*CJUVq9DBJAXFc8qwnF9BDA.png" style="height:318px; width:1000px" /></p>
<p>Shipping confidence spectrum. Companies like SpaceX are forced to test the crap out of their software, companies like GitHub allow anyone to deploy straight to prod, see what happens (sometimes employing canary deployments) and roll<strong> </strong>back if required. People like levels.io deploy to prod and use their customers to test. These are all good strategies. Also, the positioning is very approximate, don’t sue me bro™️.</p>
<p>If Boeing makes a mistake in their flight control software, people will most likely die.</p>
<p>If Tesla makes a mistake in their autopilot software, people might die.</p>
<p>If JP Morgan makes a mistake in their funding software they will lose $ and some people might see funky numbers in their accounts, leading them to changing bank.</p>
<p>If Netflix makes a mistake in their streaming software millions of people’s dates and lunch breaks will be ruined and they might not renew. They would also lose credibility with their partners.</p>
<p><a href="https://marcochiappetta.medium.com/yes-you-should-test-on-production-61f6dc61908b"><strong>Learn More</strong></a></p>