What happens is usually that you have 14,000,000 compile errors. Well, congratulations! That's the difficult part over. Now it's time to relax! Start at error 1, and fix it. Repeat. Every now and again, build. Once it builds again, it will usually work; if not, it's always something quite simple. If you have enough asserts in your code, then you can be doubly confident that there's nothing wrong with the new code.
I've had good success with this approach, for all sorts of changes, large and small. I've given up being surprised when the result just builds and runs.
I have no real idea, how you would do this reliably in a large program written in something like python. Sure, you'd fix up your tests easily enough... but then what? Don't you have a program to maintain as well? :)
Jonathan Blow wrote about this years ago: http://lerp.org/notes_4/index.html
Anyway, while it was a - slight :) - exaggeration for effect, even in well-factored code small changes can have a wide-ranging repercussion.
> There's often one corner case that works just a little bit differently.
You might just as well miss that one corner case in your test suite. This is the problem with tests - you can never be sure.
I'm not saying it can't go wrong when you're finished - it just usually doesn't. And it just doesn't take much effort to fix when it does.