程序员在编写代码的同时编写程序员测试。
有程序员测试失败了？
开发人员必须时时刻刻都要编写程序员测试。
合格的程序员测试夸大了它产生的破坏。
XP涉及两种测试：程序员测试和客户测试。
XP talks about two kinds of tests: programmer tests and customer tests.
程序员测试使开发人员有信心相信他们的代码能够工作。
Programmer tests give developers confidence that their code works.
团队应该拥有程序员测试和客户测试的自动化套件。
The team should have automated suites of programmer tests and customer tests.
团队应该有一些必须在每次集成之前和之后运行的程序员测试。
The team should have programmer tests that must run before and after each integration.
程序员测试应该实现自动化，并且要给出清楚的通过或失败结果。
Programmer tests should be automated and give a clear pass or fail result.
在这里我将讨论程序员测试，并将在下个月讨论客户测试。
I'll talk about programmer tests here, and cover customer tests next month.
开发人员只有在通过所有程序员测试后才可以将代码检入到源代码资源库中。
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.
它还已经通过了数千名其他程序员的测试，所以为什么不使用它呢？
It has also been tested by thousands of other programmers, so why not use it?
这种恶性循环就是为什么大多数程序员讨厌测试人员告诉他们代码出现问题的原因。
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.
比如，解放程序员，让他们探索测试。
单元测试是从程序员的角度编写的。
程序员通常不必测试运行程序的用户是否有权读取数据文件和设置系统时间。
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.
好的测试套件执行得足够快，以至程序员可以在每个测试发生重大变化之后运行这些测试，有可能一天运行几十次。
Good test suites execute quickly enough that programmers can run them after each and every significant change, potentially dozens of times a day.
对于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.
它不但激发程序员去编写测试用例，而且还通过“Youbrokethebuild ！”游戏促进了团队之间的合作和融合。
It not only motivates programmers to write tests, it also promotes teamwork and bonding through "You broke the build!" games.
应用推荐