DEV Community

Discussion on: Why Testing After Is a Bad Practice

Collapse
 
jankapunkt profile image
Jan Küster

TDD is a must when requirements are clear and distinct but a waste of time when reqs are fuzzy. First get all requirements together then do the tdd - that's at least my premise.

Collapse
 
mbarzeev profile image
Matti Bar-Zeev

For sure. At least you have a clear indication that the spec you got is not complete very early in the process.

Collapse
 
jankapunkt profile image
Jan Küster

That's nearly every time the case even with true domain experts we often face vague or contradictory requirements.