4 ms·
Except in order to have a checklist you have to have your design and implementation up front which is out of reach for most developers. If were testing high le
by thinkingkong 9y ago
Except in order to have a checklist you have to have your design and implementation up front which is out of reach for most developers.
If were testing high level results in multiple cases thats cool. But a lot of the time youre going to try different approaches that may modify or involve changing your output.
- hyperpallium 9y agoTDD is waterfall
- lazyasciiart 9y agoNot really. You can definitely practice TDD in two week sprints.
- darylfritz 9y agoCare to clarify this? I've seen plenty of Agile shops that practice TDD.
- hyperpallium 9y agoI was summarizing the parent. Although, a few other comments here better put my point, that TDD and unit testing in general, freeze your interfaces. Because interfaces define the functionality of modules, this forces your choice of modularity upfront. This is fine, if your already have a fair idea of how to architect your problem. But if you don't, it makes it harder to refactor your interfaces (in the same way that clients depending on your interfaces does). Of course, you can rewrite the tests, since you have control over them; it's just harder. And you don't have the TDD raison d'etre reassurance of working tests for this refactoring, of interfaces. Higher level function tests, yes; unit tests, no.
- s73ver 9y agoNo you don't. You just need to know what the unit you're currently working on does. And if you're working on it, you should know what it does. If you don't, that's a sign that maybe you need to have a conversation with someone.
- seanmcdirmid 9y ago> You just need to know what the unit you're currently working on does. Which means the system design must be obvious enough that you have well defined lowly coupled units in the first place.