Tourmaline Code about Test-Driven Development

Is it worth spending 15–35% more time upfront to get 40–90% fewer defects later? In the first issue of Tourmaline Code, we explore when TDD (Test-Driven Development) pays off and under what conditions it starts to work.

For managers and clients, this issue will help gauge whether it's worth switching to TDD. Inside, there's a table showing when tests before code are justified and when they're not, plus seven conditions without which the approach won't work.

For team leads, it will help planning the transition from “tests after code” to “tests before code”: what adoption rests on, what objections you'll hear from the team, and what small first step you can take.

For developers, it's a chance to see TDD in practice: how a good test differs from a bad one, how to break down the frontend and backend into layers for testing, how to shorten the TDD cycle in embedded, and how to apply screenshot testing to layouts.

At the end of the issue, there's a map of our open materials on the topic: talks, workshops, and project repositories. All QR codes in the issue are clickable, so you can dive deeper from any section.

Enjoy reading! Send your feedback and ideas to our email — we'll read everything and respond to everyone.