This should be titled "I don't know how to write good tests, so I consider them pointless".
> They need constant updates,
Good tests don't. They test one specific thing and only change when you change that specific behavior.
> they slow everything down.
They speed everything up, because otherwise you need to test your entire app every time you make a change. A good suite of tests gives you high confidence a change doesn't regress anything and means you can review, submit, and deploy it much faster.
I work on a large product, and I specifically own the framework that generates and powers our UI, API, and backend all from one set of config files. I almost never need to modify tests when adding features - the tests are resilient and I simply write new tests for the new feature.
> I have worked as a freelancer on client projects. Almost none of my clients had a good test suite
The kind of projects that have to hire freelancers might not have the best codebase, news at 11.
> They need constant updates,
Good tests don't. They test one specific thing and only change when you change that specific behavior.
> they slow everything down.
They speed everything up, because otherwise you need to test your entire app every time you make a change. A good suite of tests gives you high confidence a change doesn't regress anything and means you can review, submit, and deploy it much faster.
I work on a large product, and I specifically own the framework that generates and powers our UI, API, and backend all from one set of config files. I almost never need to modify tests when adding features - the tests are resilient and I simply write new tests for the new feature.
> I have worked as a freelancer on client projects. Almost none of my clients had a good test suite
The kind of projects that have to hire freelancers might not have the best codebase, news at 11.