The shift-right approach to software testing mandates that tests are run as close to the production environment as possible.
The main aim of shift-right testing is to catch defects and problems that can only be catch at that time and context in the software development cycle.
A growing number of organizations are using test automation frameworks to achieve this goal.
In this blog post, we will explore when and why you should shift-right tests in production and how you can go about doing it safely and effectively.
Follow Cerberus Testing for more open-source test automation.
Why testing in production
There are several reasons why shift-right testing in production is gaining popularity.
First and foremost, it allows you to catch bugs and issues that may not be apparent in lower environments such as development or staging.
This is because the production environment is typically much closer to the real-world conditions under which your software will be used.
As such, it is more likely to uncover defects that only occur under certain conditions or with certain data sets.
In addition, shift-right testing allows you to verify the stability of your user experience in production.
This is important because even if your software is technically sound, poor performance or usability issues can still lead to customer dissatisfaction.
Finally, shift-right testing gives you the ability to monitor customer journeys and track how they use your software in the wild.
This information can be used to improve the design of your software or to make changes that will improve the user experience.
When to test in production
Shift-right testing in production is not something that should be done indiscriminately.
There are certain circumstances under which it is more appropriate than others.
In general, you should consider shift-right testing in production if you need to verify any of the following: