If you are going to diminish risk through testing as early as possible in the development process, you have to first be able to estimate the
threat of damage caused by these issues your testing exposes.
The problem with such a risk-based approach is that it usually takes a huge amount of time – time that Agile teams often don’t have when trying to continuously test to keep the DevOps cycled flowing.
For many teams in this sticky situation, the answer is to either test everything exhaustively, or test at random. As we all know, neither of these solutions are actually very helpful.
Read this paper to learn about a simpler approach to risk-based testing.