The shift-right concept originates from testing. But agile and DevOps teams also can use it to improve their systems and service to the client. However, there is a complicating factor: Different people have different explanations for what shifting right is. Let’s look at the different forms of shifting right, what the potential benefits are, and who should ideally be involved in your shift-right process.
Shifting your testing either left or right can meet different needs and improve different aspects. How do you know whether to make a change? Let your test cycles be your guide. Just like when driving a car with a manual transmission, if the engine starts to whine or you’re afraid you’re about to stall out, switching gears may be just what you need.
When it comes to testing in DevOps, more than simple regression checking can be automated. By shifting right in the lifecycle and testing in production, you can analyze the undefined, unknown, and unexpected by relying on real traffic and unpredictable test input. With shorter implementation and release cycles, testing and production come closer together.