My TDD rule of thumb is that tests should be moist but not drenched.
我的TDD 经验法则是，测试应该是湿润的，但是不要湿透。
If, on the other hand, you have TDD experience, please share some of your answers to these questions.
换个角度来说，如果你已经有了充分的TDD经验，请与大家分享一下你对这些问题的答复。
To show the design benefits of TDD, I need a problem to solve.
要展示TDD的设计优点，我需要用到一个待解决的问题。
TDD can inform some of your architectural decisions, but you cannot begin a project without an architectural vision.
TDD可以告诉你某些架构决定，但是你无法在没有架构设计的情况下启动项目。
TDD encourages developers to write a failing test when writing the first test for some new functionality.
在为一些新功能编写第一个测试时，TDD鼓励开发人员编写失败的测试。
I use EDD and TDD together, can't imagine using one without the other.
我把EDD和TDD放在一起用，而且无法想象只用一个是什么状况。
Several of the practices outlined here can be categorised as general Test Driven Development (TDD) practices.
本文概述的实践中，有一些可归类到常用的测试驱动开发(TDD)实践。
The most important lesson you should have learned so far is that TDD is simple.
迄今为止，你应该明白一条最重要的道理就是TDD很简单。
I'll also address some other sticky design questions about TDD, such as if and when to test private methods.
我还将解答其他某些棘手的TDD设计问题，例如是否测试及何时测试私有方法。
Similarly TDD practice requires a unit testing tool and a refactoring tool.
TDD实践也需要单元测试工具和重构工具的配合。
The normal TDD approach at this point is to stop testing and start fixing until the test passes.
这时，标准的TDD方法是停止测试并且开始进行修改直到测试通过。
TDD recommends beginning testing early and continuously testing, such as with each system build.
TDD建议及早开始测试并持续测试，例如测试每个系统版本。
Tests start in the provisional project, especially when they are used for TDD-style programming.
测试从临时项目开始，特别是在TDD风格编程中用到的测试。
Test-driven development (TDD) is a key practice in agile software development.
测试驱动的开发 (TDD)是敏捷软件开发中的关键实践。
It also used a simple scenario to illustrate a TDD style of development.
此外还使用了一个简单的场景来演示TDD风格的开发。
If you are new to TDD these questions probably sound familiar.
如果你还是TDD新手，这些问题可能会听起来很熟悉。
TDD increases your production because it serves as a thinking-aid.
测试驱动开发可以提高生产效率，因为它有助于思考。
With TDD the tests are thought out and created as the code is implemented.
使用测试驱动开发，在实现代码时，就要仔细考虑测试，并建立起测试。
Higher quality is a side effect of TDD.
质量的提升是TDD的一个副作用。
Trying to offer TDD as an algorithm generator is dopey and it's just going to make it easy for people not to take TDD seriously as a valid design technique.
想以测试驱动开发来构造算法的做法是愚蠢的，他只会使人们更容易误认为测试驱动开发不是一个有效的设计技术。
You cannot derive a complete architecture with TDD.
你不能通过TDD得到一个完整的架构。
TDD puts the test before the code.
TDD将测试放在编码工作前。
One of the common agile development practices is TDD.
常见的一种敏捷开发实践就是TDD。
Supports TDD by providing a powerful data binding validation framework for WPF.
通过为WPF提供强大的数据绑定验证框架支持TDD。
TDD facilitates this because you must have small chunks of functionality for testability.
TDD 能够促进这种做法，因为为了进行测试，必须把软件分解为小的功能块。
Some members of the Agile community suggested that BDD was merely "TDD done well".
敏捷社区中有些成员认为BDD就是“做得比较好的TDD”。
As often happens for a while after TDD is adopted productivity slowed while quality increased.
像往常一样，TDD用过一段时间之后，质量上升了，而开发速度却下降了。
Rigorous adherence to TDD naturally creates methods that adhere to composed method.
严格遵守TDD会自然地产生符合组合方法模式的方法。
Normal TDD writes only enough code to make a test fail.
标准的TDD只编写能够使一个测试失败的足够多的代码。
应用推荐