3 ms·
Where I come from, unit-test-driven-development tends to be a waste of resources. The interfaces will change so much during development that anything you write
by shadowgovt 4y ago
Where I come from, unit-test-driven-development tends to be a waste of resources. The interfaces will change so much during development that anything you write initially is guaranteed to be torn up. The one exception is if you're writing an interface that crosses teams; for "ship your org chart" reasons, we not only can, but must assume that interface is stable enough to mock and test against (and a knife-fight is necessary if it isn't).
However, getting the client to agree that their design feature is satisfied by a specific set of steps, then writing software that satisfies that request, is a form of test-driven-development and I support it.