TL;DR
In the previous reading club, we shared the article about SSL Certificates. Today, we gave you two approaches on how to create a risk heat map for application features.
The problem is how to prioritize which features to cover with automation because we always have too many features and not enough time. In the Visual Risk & UI Automation framework, you can read how to create a feature risk heat map. The idea is to put features into a diagram where the Y-axis is features the Impact of Failure, and the X-axis is features the frequency of usage. Automation prioritization using Risk Mapping presents an implementation of features risks heat map.
