Write tests for the servlets and JSPs.
为servlet和JSP编写测试。
I show them how to write tests using modern tools.
我告诉他们如何使用现代工具编写测试。
Jeff: "I just fired Mark because he doesn't write tests."
Jeff：“因为Mark不编写测试，刚被我解雇了。”
And as they write tests, the customers come to expect tests.
这样就造成了编程人员编写测试，而客户期盼测试的情形。
Many programmers who don't write tests first don't even know it's an option.
许多没有先编写测试的程序员甚至不知道还可以使用这种方法。
You need to take small steps and write tests that force you to take more steps.
您需要采取一些较小的步骤，然后编写迫使您要采取更多步骤的测试。
It's not hard to write tests that cover simple methods like setters and getters.
编写覆盖像setter和getter这样简单方法的测试代码并不难。
The true power of Rails is that you can write tests as fast as you can write code.
Rails真正强大的地方在于，您可以像编写代码一样快速编写测试。
Once you partially test all the classes, write tests that cover any uncovered methods.
对所有类进行专门测试后，还要为所有未覆盖的方法编写测试代码。
By the same token, it's more effective to write tests that you know you'll run often.
出于同样的原因，编写那些您知道将要经常运行的测试程序会更有效些。
You have to get used to the idea that you can and should write tests before you write code.
您必须习惯这种思想，在编写代码之前，可以并应该编写测试。
Even if they know how and think it's a good idea, many people still don't write tests first.
即使他们知道如何去做，并认为它是一种好的想法，但许多人仍然没有先编写测试。
Cucumber on the other hand lets users write tests in plain text files in almost free form English.
另一方面，Cucumber让用户用纯文本文件且不受英语的限制来编写测试。
Using Cobertura's reports, you can identify the untested parts of the code and write tests for them.
利用Cobertura报告，可以找出代码中未测试的部分并针对它们编写测试。
You write tests before you write the code, solidifying your understanding of what the code needs to do.
先写测试，再编写代码，这样可以巩固您对代码所需执行的操作的理解。
If I frequently don't write tests, then pretty soon I've got a pile of code that isn't covered by tests.
如果我经常不写测试，那么不久会有一堆代码没有经过测试。
In fact, if I tried to write tests for this code, they would technically run but wouldn't ever logically work.
事实上，如果我试着为这段代码编写测试，从技术方面来说它可以运行，但是无法按照逻辑工作。
As you write tests first and get them to pass, you're letting the code tell you what it wants to do and become.
在您先编写测试并通过测试这个过程中，您正在让代码告诉您它想要做什么，以及会成为什么。
You might say that they each allow you to write tests using their own particular dialect of convenience functions.
可以认为它们分别提供一种方便的测试 “方言”，可以用这些 “方言”编写测试。
As a programmer, you should write tests before you write code, then write just enough code to get the tests to pass.
作为一名程序员，应该在编写代码之前编写测试，然后只编写足以让测试通过的代码即可。
More often than not, if they do write tests, they're typically very simple, covering the method's main functional aim.
而且如果需要编写测试，通常都是十分简单、覆盖方法的主要功能目标的测试。
Write tests in a "just-in-time" fashion, when you find the need to modify a class that doesn't have good (or any) tests.
当您发现有必要对一个未经很好测试(或者根本就没有测试)的类进行修改时，请“随时”编写测试。
It not only motivates programmers to write tests, it also promotes teamwork and bonding through "You broke the build!" games.
它不但激发程序员去编写测试用例，而且还通过“Youbrokethebuild ！”游戏促进了团队之间的合作和融合。
XP demands that you write tests before you write code, so a simple design is one that grows over time in a test-first manner.
XP要求您在写代码之前先写测试，所以简单设计是以一种测试当先(test - first)的方式逐渐增长的。
You need a tool that tells you which parts of a program are not being tested so you can write tests for those parts and find more bugs.
您需要有一个工具告诉您程序的哪些部分没有测试到，这样就可以针对这些部分编写测试代码并找出更多bug。
You need a tool that tells you which parts of a program are not being tested so you can write tests for those parts and find more bugs.
您需要有一个工具告诉您程序的哪些部分没有测试到，这样就可以针对这些部分编写测试代码并找出更多bug。
应用推荐