除非你有一个类、组件、或者一段已经写好的代码，并且在现有的项目已经测试通过。不要认为这将是很容易的。
Unless you have a class, component, or piece of code already coded... and has been tested thoroughly... and is in production from an existing project, don't think it will be easy.
在编写实际的生产代码时，您希望充当一回jerk开发人员的角色，只完成最少量的工作来使测试通过。
When you're writing the actual production code, you want to play the part of a jerk developer who will only do the minimum amount of work possible to make the test pass.
所有代码都在SuSELinux 8.2上和NetBSD -current的最新构建上测试通过。
The code has been tested on both SuSE Linux 8.2 and a recent build of NetBSD-current.
现在仅仅编写足够使测试通过的代码（这里有两个测试）。
Now I can write just enough code to get the tests (there are now two) to pass.
作为一名程序员，应该在编写代码之前编写测试，然后只编写足以让测试通过的代码即可。
As a programmer, you should write tests before you write code, then write just enough code to get the tests to pass.
正如我上月所述，编写足够的代码以使测试通过可以简化程序代码，从而有更多的精力关注手边的工作。
As I said last month, writing just enough code to make a test pass keeps code simpler and keeps me focused on the task at hand.
我们用的是测试驱动的方法，首先写一个我们希望通过的测试，一旦这个测试通过，我们再回头看我们可以怎么来优化代码。
We did it test-driven, starting with a test that we wanted to succeed and once it passed we looked into how we could improve the code.
这种“编写一个测试，编写足够的代码来使测试通过，重新进行测试”方法是您每天都在经历的XP开发流程。
This "write a test, write just enough code to get it to pass, rerun the test" approach is the xp development flow that you should experience every day.
TDD要求您反过来做：先编写测试，并让它来提示如何编写可以让测试通过的代码。
TDD requires that you do the opposite: write the test first and allow it to inform how you write the code that makes the test pass.
在运行Jester之前，所有对没有修改的源代码的单元测试都必须测试通过。
Before you can run Jester, all the unit tests must pass with the unmodified source code.
在运行Jester之前，所有对没有修改的源代码的单元测试都必须测试通过。
Before you can run Jester, all the unit tests must pass with the unmodified source code.
应用推荐