DEV Community

loading...

Discussion on: How I learned TDD (the hard way)

Collapse
daliborp profile image
Dalibor Plavcic

It is really great to see even more people practicing TDD on real projects :respect:

What really helped me to grasp TDD concepts was Dan North's introduction to Behavior Driven Development (BDD) which make TDD even more natural: dannorth.net/introducing-bdd/.

I think it could be really helpful for readers to mention BDD and benefits it brings to the table.

Collapse
tinydevops profile image
Jonathan Hall Author

I like BDD, but it doesn't apply to every project. And I think that BDD and TDD are very distinct. BDD has a cycle time typically of days, where as TDD has a cycle time of seconds.

Collapse
daliborp profile image
Dalibor Plavcic

Where did you get that idea/notion of BDD? I'm asking because my team applies BDD concepts to define user stories and acceptance criteria (days/weeks, analysts do that), while developers use BDD to confirm acceptance criteria are implemented correctly at unit/integration/e2e level. Developers also write tests in a TDD manner.

It would be great if you could provide a little bit more info/references to the thing you are stating about TDD/BDD or personal experience would also be nice :)

Thread Thread
tinydevops profile image
Jonathan Hall Author

BDD is usually considered most applicable to user-facing products (i.e web or mobile apps), and teams with non-technical product owners.

For other projects, it can just be unnecessary overhead.