We know that having tests around our code buys us confidence and the ability to make changes with less fear of breakage. But reaching 100% code coverage can often feel like it has quickly diminishing returns: we can spend a lot of time writing tests that may or may not ever save us from a regression.
In today’s episode, guest chef Chelsea Troy shows us a way of writing tests using a risk-oriented perspective. She’ll demonstrate how she examines systems to determine where effort spent on tests is likely to have the largest payoff. In the process you’ll see why judging risk in a system is not as simple as determining the parts that are most likely to break. Enjoy!