合格的程序员测试夸大了它产生的破坏。
XP涉及两种测试：程序员测试和客户测试。
XP talks about two kinds of tests: programmer tests and customer tests.
团队应该拥有程序员测试和客户测试的自动化套件。
The team should have automated suites of programmer tests and customer tests.
开发人员只有在通过所有程序员测试后才可以将代码检入到源代码资源库中。
A developer cannot check code into the source code repository until all the programmer tests pass.
在过去五年中广泛采用的程序员测试是由显著的生产率和得到的代码质量所驱动的。
The widespread adoption of programmer testing over the past five years has been driven by the demonstrable productivity and quality of the resulting code.
程序员测试告诉开发人员系统是不是在任何时刻都能正常运行(象客户定义的那样)。
Programmer tests tell developers whether the system works (as defined by the customer) at any point in time.
最重要的是，它假设您做过程序员测试――并且这些测试 每一次都全部通过。
Most importantly, it assumes you have programmer tests -- and that they all pass all the time.
程序员测试还给予开发者重构代码的勇气，因为测试失败会立即告诉开发者是不是有地方出了问题。
Programmer tests also give developers courage to refactor the code, because a test failure tells the developer immediately if something's broken.
XP规则很简单：如果不进行程序员测试，则您不知道要编写什么代码，所以您不会去编写任何代码。
The XP rule is simple: If you don't have a programmer test, you don't know what code to write, so you don't write any code.
作为一名程序员，我常常对使用程序员测试进行编码与不使用程序员测试进行编码之间的差别感到吃惊。
As a programmer, I am frequently amazed by the difference between coding with programmer tests and coding without them.
在计算机科学中，单元测试是一个有程序员测试源代码的个体单元是否适合使用的软件检测和验证方法。
In computer programming, unit testing is a software verification and validation method in which a programmer tests if individual units of source code are fit for use.
这种恶性循环就是为什么大多数程序员讨厌测试人员告诉他们代码出现问题的原因。
That kind of cycle of doom is why most programmers hate testers who tell them something is wrong with the code.
即使是最好的程序员，测试、复查和调试不遵循任何标准的代码也是一项艰巨的任务。
Testing, reviewing, and debugging code that does not follow any standards can be a daunting task, even for the best of programmers.
在整个代码中的适当地方，程序员编写程序逻辑来测试当前用户是否有权执行某个操作。
At appropriate places throughout the code, the programmer writes program logic to test whether the current user is authorized to perform an operation.
这种新体系结构的另一组成部分更关注一致性测试、程序员认证和产品认证(评估)。
Another building block of this new architecture is a more concentrated focus on conformance testing, certification of programmers, and certification of products (branding).
程序员通常不必测试运行程序的用户是否有权读取数据文件和设置系统时间。
Programmers don't usually have to test whether the user running the program is entitled to read a data file or set the system time.
许多没有先编写测试的程序员甚至不知道还可以使用这种方法。
Many programmers who don't write tests first don't even know it's an option.
通过简化编辑、编译和测试过程，帮助程序员提高生产力。
Making it easier to cycle through the edit, compile, and test cycle helps foster programmer productivity.
在我用那种方式向大多数程序员说明这种情况时，他们认为测试驱动的编程是一个不错的想法 ― 这之后，他们仍然不使用这种方法。
When I explain it that way, most programmers I've talked to think test-driven programming is a good idea -- then they still don't do it.
好的测试套件执行得足够快，以至程序员可以在每个测试发生重大变化之后运行这些测试，有可能一天运行几十次。
Good test suites execute quickly enough that programmers can run them after each and every significant change, potentially dozens of times a day.
尽管大部分程序员能够检查代码并测试代码的bug，但他们并不知道如何证明他们的程序将会按他们所设想的那样去执行。
And while most programmers can examine code and test code for bugs, they do not know how to prove that their programs will perform the way they think they will.
对于Zero的RESTful资源脚本，好的文档不仅能够帮助您记住代码如何工作，还能帮助客户端程序员创建并测试其客户端代码。
When it comes to Zero's RESTful resource scripts, good documentation not only helps you remember how your code works, it can help client-side programmers create and test their client code.
它不但激发程序员去编写测试用例，而且还通过“Youbrokethebuild ！”游戏促进了团队之间的合作和融合。
It not only motivates programmers to write tests, it also promotes teamwork and bonding through "You broke the build!" games.
连续测试：在程序员增加一项特征前就完成测试程序。
Continuous Testing: Before programmers add a feature, they write a test for it.
对于程序员来说，在需要测试时、在接口另一端的程序不可用时，这种实用工具是极为有用的。
For programmers, this utility can be extremely useful when you need to test and the program at the other side of the interface is not available.
即便开发人员知道测试的益处，我们也会发现程序员们不愿意测试他们的代码。
Even though developers know that testing helps, we still see a reluctance by programmers to test all their code.
只要您保持测试和代码的同步(这是实践的关键点)，如果有程序员想知道系统能做什么，他或她可以参看测试。
As long as you keep your tests and code synchronized (and that's the whole point of the practice), if a programmer wants to know what the system does, he or she can look at the tests.
作为一名程序员，应该在编写代码之前编写测试，然后只编写足以让测试通过的代码即可。
As a programmer, you should write tests before you write code, then write just enough code to get the tests to pass.
忽略质量控制——时间压力有时会让程序员或项目团队有意跳过测试过程。
Neglecting quality control - time pressure can sometimes cause programmers or project teams to be tempted to skip testing.
忽略质量控制——时间压力有时会让程序员或项目团队有意跳过测试过程。
Neglecting quality control - time pressure can sometimes cause programmers or project teams to be tempted to skip testing.
应用推荐