This. We write unit tests when we do math on financial transactions, clear cut migrations of data, and other very well-defined, high risk circumstances. The ot

This. We write unit tests when we do math on financial transactions, clear cut migrations of data, and other very well-defined, high risk circumstances. The other use-case for tests is explaining the expectation to new developers / teams under tight timelines. Example - we had a "surge" team come in - we were writing software that pulls data out of emails in hundreds of formats. We set up infrastructure for it that says - here is your input, here is your ouput, here is 100 sample records, make unit tests pass for them. This worked amazingly well when you had a team writing RegEx, another team writing csv stuff, one team using ML, etc. Basically, the goal was "make it work, in 2 weeks, no one will ever touch this code again." Btw, the latter is ALWAYS, ALWAYS a lie - if a company sinks a few hundred thousand into a project, you WILL touch it again. Anyway, this was more of a rant - basically unit tests ARE useless 90% of the time. Unit tests in Angular that are basically integration tests are absolutely disgusting. Keep in mind that if you have coverage, any time you modify a class, you are now fixing a bunch of broken tests. I guess that's why I am for testing individual methods and SRP.