The thoughts here are a bit too focused on the costs of testing. Although deeper questions are asked about your own judgement of whether to test something or no

The thoughts here are a bit too focused on the costs of testing. Although deeper questions are asked about your own judgement of whether to test something or not, it doesn't consider the benefits. I wrote about this the other day in another post: - Test give the ability of other developers to be productive on the project faster. 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 happens, 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 then permeates into other areas of your business. (Sorry for the self plug) This is why I created Data Caterer (https://github.com/data-catering/data-caterer https://github.com/data-catering/data-caterer) to try provide a fast and reliable tool to help with end to end testing.