Looking for your best takes for and against TDD (test driven development). Let’s go!

The hottest most controversial dev discussions. Found something you'd like to share? Add it in the thread 👇


controversy.dev

The post invites a discussion on the pros and cons of Test Driven Development (TDD), seeking various perspectives on its effectiveness and challenges.

To TDD, or not to TDD, that is the question

If you have the time, do it. Working for a company most of the time it means there is no time for TDD, particularly working with legacy code.

TDD is awesome! It boosts code quality and catches bugs early, making refactoring a breeze and ensuring requirements are crystal clear. Tests double as documentation and encourage modular code, but starting can be slow, and there’s a risk of focusing too much on unit tests. Some testing scenarios are tricky, and teams might resist change, but with the right approach, TDD can totally rock your development process!

IMO - TDD is optional, but tests are not. It’s obviously BETTER to write the tests beforehand in many cases, but sometimes its just not practical. But for devs on my team, they’d better be including tests in any pull request!!

Highly recommended for large projects with multiple developers. The cost-benefit may not make sense for a small project with a small team.

It takes a time, but once you’re used to it, it’s a skill that can make a difference in your job career.