Testing in Production, the safe way
Many company tests in a dedicated QA/Staging environment. Yet, bug is still catch on production.
The problem is some are impossible to catch on a non-production env. Because essentially we don’t test on the environment we run. So how we can make test in production safety without corrupted data, or interrupt workload of any existing application.
Appears in lists (1)
More like this (3)
Testing in Production: the hard parts Two of the hardest problems of testing in production are...Testing in Production: the hard parts Two of the hardest problems of testing in production are curtailing blast radius and dealing with state. In this post, I aim to explore the topic of curtailing blast radius in more detail. In a follow-up post titled Testing in Production: The Fate of State, I plan to explore the intricacies of testing stateful services in production.
The path to production: how and where to segregate test environments The benefits of a duty-segregated...The path to production: how and where to segregate test environments The benefits of a duty-segregated path to production are: 1. Debugging faster and more easily by isolating development and testing into stages. You can detect problems earlier, and feedback loops are faster. 2. Saving resources by keeping the number of production-like environments as low as possible (one or two is good).