> Either you're writing tests or you're manually running the software (manual testing) There's nothing wrong with manual testing. In fact, unless you have good

> Either you're writing tests or you're manually running the software (manual testing) There's nothing wrong with manual testing. In fact, unless you have good set of E2E tests (most companies don't), you still need manual testing. At some point manual testing may become tedious and it's can be worthwhile to automate it to certain degree, typically with a few integration tests. But well-architected systems need very few tests to be reliable. Having a lot of tests is not something you should celebrate, it's a signal your architecture sucks. And if you find yourself writing a lot of unit tests, please read this: https://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste.pdf https://rbcs-us.com/documents/Why-Most-Unit-Testing-is-Waste...