3 ms·
I would argue that "producing information" is only one benefit of tests. Having worked with decent-sized legacy code bases, another big benefit of tests is pre
by cle 10y ago
I would argue that "producing information" is only one benefit of tests. Having worked with decent-sized legacy code bases, another big benefit of tests is preventing future loss of information. Deleting tests removes those guardrails. If what you write is successful, then it will become a legacy system, and your predecessors who inherit it (and ultimately your customers) will be glad you didn't delete tests.
- indolering 10y agoI worked at a company that didn't employ any unit testing and they were terrified of updating their aging software stack because it was constantly breaking as is. I was doing greenfield work and was paranoid about losing data, so I had extensive test-coverage. I undertook multiple complex refactors of the codebase and never had a problem thanks to my unit test coverage. My code was never the cause of any major data loss and I found plenty of very serious bugs in the legacy codebase.