The article doesn't mention refactoring, and that's where the value of tests lies.

Given a complete test suite and stable interfaces, you can make substantial changes to existing code and if you break anything you'll know. It's often the difference between making changes that need to be made, and avoiding those changes because there's no safety net.

I'd be curious how the author approaches refactoring.