The headline of the article should be a hint. "3 steps to add tests on existing code when you have short deadlines" So, if you're on a short deadline and maybe

The headline of the article should be a hint. "3 steps to add tests on existing code when you have short deadlines" So, if you're on a short deadline and maybe you didn't write the code the first place, so you might not be familiar with the internals, snapshot testing is the quickest way to get confidence that you aren't causing further regressions. These aren't meant to be used forever more. Just to stop things from sliding backwards. After all, the title of the site is understandlegacycode.com. It's all about getting to a point where you can refactor and do things properly when you do get time. If that doesn't make sense, what would you suggest to do?