I think it primarily applies to frameworks, though I guess folks will say any app is a framework for folks working on it so it could apply even with bringing new folks onto an existing project.
The question is whether tests are aligned to usage scenarios/patterns. I think of it kind of using MSDN sample code as tests. I have never been in a BDD shop (though I ran some experiments at Azaleos from a spec perspective), but I have always wondered if that would provide better test organization than typical TDD approaches or you have to really plan for tests as developer documentation. We might as well argue code as documentation and how much commenting is appropriate and using jdoc/ndoc and other means (contracts?) as a specific work product given its costs for maintenance. Ron -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
