So, in other words, to use my strategy, simply write one test case class, and then always deploy to both the client and the server.
所以，换句话说，要使用我的策略，只需编写一个测试案例类，然后总是将其部署到客户机和服务器就可以了。
When we find bugs, we write a test case to expose the bug and add it to the suite prior to fixing it.
当我们发现错误时，我们编写测试案例来找到错误并在修正此错误之前将其添加到套件中。
If developers had to write code for accessibility evaluation points in every test case, that would add a great deal of work.
如果开发人员不得不为每个测试用例中的易访问性评估点书写代码，那样会添加许多工作。
Perhaps the rationale for this is that, by knowing who the owner is, you can gently prod that person to write a test case.
也许它的基本原理是，通过了解所有者是谁，您可以温和地让此人书写测试用例。
Write your test cases first, and write only enough code to make your test case pass.
首先编写测试用例，并且只编写足以让测试用例通过的代码。
Your first thought could be that it's time to refactor, but doing so would break the first rule of refactoring, which is to write a test case.
您首先想到的可能是：到重构的时间了，但这样做将打破第一个重构规则，即将编写一个测试用例。
Code coverage indicated we were done after one test case, but CC forced us to write an additional one.
代码覆盖率指示我们已经在一个测试用例之后完成了此操作，但CC却会强迫我们编写额外的测试用例。
Write a test that fails We selected the test that seemed the easiest to implement (although in this case they were all simple) and wrote it.
写一个失败的测试：我们选择了一个最容易实现的测试（虽然在这个例子中所有的都很简单）来实现。
JUnit has a bit of this pattern language approach, because it can help you write a test case.
JUNIT使用了一点模式语言的方法，因为它能帮你写一个测试用例。
Naturally, I also write a quick test case to verify my check actually averts NullPointerExceptions, as shown in Listing 4.
很自然，我也会编写一个快速测试用例来验证我的检验是否真能避免NullPointerException，如清单4所示。
Accordingly, I can write a test case to verify XMLUnit's behavior, as shown in Listing 6.
相应地，我可以编写测试用例来验证XMLUnit的行为，如清单6所示。
The following steps cover how to develop the EJB, set up the Cactus framework, write your test case, and unit test with the test case that you will create.
下面几个步骤是关于如何开发e JB、安装Cactus框架、编写测试案例以及对将创建的测试案例进行单元测试的。
NUnit lets you write a test case in the same language and environment as your application.
Nunit允许你用与应用程序相同的语言和环境来写测试用例。
Then, you would write your test case to verify that the aspect correctly interacts with the target, as shown in Listing 4
然后，编写测试用例以验证方面正确地与目标交互，如清单4 所示
One of the practices of test-driven development (TDD) is to write the tests first, then "do the simplest thing that could possibly work" -- in this case, return 6.
测试驱动的开发 (TDD)中的一个练习就是首先编写测试，然后执行可能运行的最简单的操作 —— 如本例中的 return 6。
Bittner and Spence write that special requirements (requirements that do not apply to the whole system) can be placed into a use case, and could thus be accessible to the high-level test case writer.
Bittner和Spence曾经写到，可以将具体的需求(并不运用到整个系统的需求)置于一个用例中，这样对高水平测试用例的编者来说也更容易接近。
Then I'll write another test case and see if I can figure out the algorithm at that point.
之后再写一个测试用例，看那时我是否能想出这个算法。
Then I'll write another test case and see if I can figure out the algorithm at that point.
之后再写一个测试用例，看那时我是否能想出这个算法。
应用推荐