当您遵循 SOLID 原则和 DI / IoC 概念来使您的类可测试时（最重要的是，大多数测试通常位于演示文稿中的 MVC 类型），TDD 通常非常容易使用正确的模式来做正确的事情。
I think that NerdDinner and CodeCampServer have both extensive unit tests, and are developed in TDD fashion, but it was really a long time from my last check on these projects...
TDD is generally really easy using right patterns for right things, when you follow SOLID principles and DI / IoC concepts to make your classes testable (and most important, sort of MVC for the presentation where usually most of your tests lie).
发布评论
评论（2）
我认为 NerdDinner 和 CodeCampServer 都有广泛的单元测试，并且是以 TDD 方式开发的，但距离我上次检查这些项目已经过去了很长时间......
当您遵循 SOLID 原则和 DI / IoC 概念来使您的类可测试时（最重要的是，大多数测试通常位于演示文稿中的 MVC 类型），TDD 通常非常容易使用正确的模式来做正确的事情。
I think that
NerdDinnerandCodeCampServerhave both extensive unit tests, and are developed in TDD fashion, but it was really a long time from my last check on these projects...TDD is generally really easy using right patterns for right things, when you follow SOLID principles and DI / IoC concepts to make your classes testable (and most important, sort of MVC for the presentation where usually most of your tests lie).
试试这个，它结合了 TDD、BDD 和一点 DDD
UBADDAS - 用户行为和领域驱动的接受故事
在这里找到 - http://kernowcode.github.io/UBADDAS/
它会产生这样的控制台输出
Try this one, It combines TDD, BDD, and a little DDD
UBADDAS - User Behaviour and Domain Driven Acceptance Stories
found here - http://kernowcode.github.io/UBADDAS/
It produces console output like this