So I generally consider my team to have pretty ok attitudes when it comes to quality, but a couple of months ago I found out while doing an audit (with the team) of all our automated tests that we have very little unit test coverage. Some parts of the system have none at all, even the more modern things we’ve built.
I’ve been getting soft resistance to my influencing, arguments like it adds time and “unit tests are great, but I don’t think it would add value to this particular part of the system”. Since I’m not a programmer (I dabble) and have not written unit tests before, it’s hard for me to come up with non-general arguments against this. Everyone is aware of the advantages of unit testing, but it feels like no one really believes it in their hearts. We’ve talked about how they are small and quick to run, they identify problems quickly/early/while devving. They make refactoring code safer, and provide living documentation of what behaviour is expected… Everyone is aware of all these things, and when we talk no one is outspokenly against unit testing - just every single time they have an opportunity to write some, there is an excuse not to. xD idk if this could be a confidence issue where no one is sure how to write good unit tests, although I don’t have any guidance to give on this matter.
Do you have any good resources for devs that I can share that gives a dev’s perspective on why unit tests are great, stories from developers who started using them or just particular ways of framing the discussion that you’ve found effective? Or any resources on how to write effective unit tests, examples etc.
Thanks in advance