Ask HN: Is TDD still a thing in 2018?
4 comments
I find it useful for new projects. It allows me to define acceptance of core functionality and features.
For established projects, not so much. This is especially true for people new to the project as they typically don’t yet know the full system and it may push them to recreate some functionality that already exists.
For established projects, not so much. This is especially true for people new to the project as they typically don’t yet know the full system and it may push them to recreate some functionality that already exists.
There are times where TDD makes a lot of sense, I find it to be quite useful in situations where you have some sort of known interface you need to implement exactly. In that case writing the tests first tends to save a lot of time overall.
TL;DR yes, it still works well.
Ignore any hype. TDD/BDD is great for anyone who has seen some shit hitting the fan in his/her professional life.
In fact, jobs not asking for TDD/BDD will probably be throwing shit at you.
Ignore any hype. TDD/BDD is great for anyone who has seen some shit hitting the fan in his/her professional life.
In fact, jobs not asking for TDD/BDD will probably be throwing shit at you.
TDD usually means tests-first development. It’s possible to have tests-required without TDD or tests-first.
A few years ago, it was the in-thing and everyone was preaching it like it was some type of technological savior, but I don't see many articles about it anymore.
So is TDD/BDD still cool, or has it been added to the IT scrap pile?
NOTE: I am not asking about Unit Tests - just about TDD/BDD as a development practice for a mid-level developer.