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)
Why Doesn't Webpacker Use My Test Config When I Run Rails Tests? — “Here’s something you...Why Doesn't Webpacker Use My Test Config When I Run Rails Tests? — “Here’s something you might not expect: when running Rails tests, Webpacker will load the development webpack config instead of the test config by default.”
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.