As software development approaches have evolved over the past two decades, various agile models have... Tagged with tes, tdd, test, programming.

Maxi Contieri

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Test-Driven Development (TDD) has gained popularity because it works to resolve the speed vs quality dilemma. Using TDD for software development is a more balanced approach emphasising three primary tasks: coding, testing, and designing. For each feature, I write 20-25 tests to cover all possible use Alternative option: a test framework abstracted.

Why Every Developer Should Employ Test Driven Development

I wish articles like these would show some real data which shows TDD is better, rather than just re-hashed opinion which also doesn’t really address any of the criticisms of TDD.
Interestingly I did some googling and found studies from as far back as 2003, so the article is incorrect that this is a new approach. But there are loads of studies out there, some which suggest there’s a positive effect but I struggled to find something which summarised the data.
The article also doesn’t discuss how this can be more or less applicable to different types of development projects. In my limited experience, TDD can be great for testing business logic but can be a nightmare for testing things like UIs. I’d also say it works well for integration tests, but unit testing the specific interactions between components/classes can mean you’re effectively implementing the whole thing in your head while writing tests - on both backend and frontend.