It was touched on at the beginnning of the article but something I find overlooked about having tests are: - Ability of other developers to be productive on th

It was touched on at the beginnning of the article but something I find overlooked about having tests are: - Ability of other developers to be productive on the project. Having tests tells other developers the intended behaviour and notifies them when they have broken it. - Flow on effect of slow or large test suites. It demotivates developers to write new tests, run existing tests and accept failures if there are too many. This then leads to a lack of confidence, trust deteriorates between team members and development pushes towards going faster than being stable. Eventually, once enough bugs occur or a large incident, then you go back to looking at tests again. If you have fast and reliable test suites, a developer wants to run and add to them. Developers feel that this is a high quality project that needs to be well maintained. This culture them permeates into other areas of your business.