I don't work in Banking but I do work in healthcare and testing is required. No code makes it to Master if it doesn't have any tests. We do unit tests, integr

I don't work in Banking but I do work in healthcare and testing is required. No code makes it to Master if it doesn't have any tests. We do unit tests, integration and EtoE testing with a few full-on regression tests being thrown in here and there when we do a major upgrade. At first, I thought that maybe we were kind of overdoing it but as the codebase is expanding, I find it actually quite easier to refactor old code when I know there is a test covering that piece of code that I have just replaced. As for the excuse: there is no time to write tests, you simply need to change the estimate of your story during the sprint planning. Even for my own personnal projects, I write tests. It's good practice and it makes me more confident when I add a new functionnality.