I stumbled across this post today, which represents (I think) a widely held belief that unit tests are bad. The argument here seems to be:Thanks for reading The Daily Developer! Subscribe for free to receive new posts and support my work. Unit test coverage doesn't guarantee that features actually work, only that regressions can be caught

Lobsters is a community-driven platform for sharing and discussing links to articles, tutorials, and projects related to technology and programming. Readers can learn about a wide range of topics, from software development and system administration to cybersecurity and artificial intelligence. With user submissions, comments, and voting, Lobsters provides a platform for collaborative learning and knowledge sharing among technology enthusiasts.

Lobsters

The post discusses the misconception that unit tests are harmful, highlighting that it is actually the poor quality of unit tests that can cause issues. It emphasizes the importance of listening to the code and using unit tests as a tool for code refactoring and design guidance.

Unit tests considered harmful? No.