February #MidsTest with Ben Fellows

Not all testing is equal, because not all aspects of a software product are equal. Some aspects are more important than others or are more likely to fail in important ways. At CELCAT, we view risks in testing as anything that could go wrong in our product for the customer. The more likely something is to go wrong, or the bigger impact it will have, then the higher the risk and the more time we prioritise to testing it.
The problem is risks can be difficult to identify and agree upon. To help solve this problem, we employ a technique known as Riskstorming. Riskstorming is an idea originally developed by by Beren Van Daele (@isleoftesting) as a way to “focus a team on quality and risks”.