# [[Shift-right testing]] Shift-right testing is a counter-movement to the [[Shift-left testing]] movement. While shift-left advocates testing earlier in the [[Software Development Lifecycle|SDLC]], shift-right advocates moving testing in the other direction, testing in production. ## Benefits of shifting right - You don't need an environment other than production, reducing environment and infrastructure costs. - Testers can achieve better test coverage, because all the components are operational and integrated. - Some types of [[Operational testing]], particularly involving [[Disaster Recovery]] scenarios or [[Chaos Engineering]] experiments, are best done in production. - Shift-right testing acknowledges that continuous deployment sometimes entails pushing to production before features are thoroughly tested. - It can sometimes, but not always, involve crowdsourcing testing, which utilizes the early adopter user base as testers. This type of testing can be cost-efficient. ## Shift-right testing in the wild [[Google]] has always been a strong example of this movement. Their Google Labs clearly distinguishes which products are works in progress as compared to the more polished products in their line. This approach prioritizes quick turnaround on new builds and bug fixes, letting users submit bug reports and continuous feedback. ## Main criticism of shift-right testing The main criticism for shift-right and [[Shift-left testing]] is that they still refer to an [[Software Development Lifecycle|SDLC]] that is linear, whereas most companies have shifted to a more cyclical or [[Agile]] approach that does not clearly have a beginning, end, left, or right. The term [[Continuous Improvement|Continuous Testing]] has risen in popularity because of this.