In this example, for clarity, we left some of the validation inside the test method.
在本示例中，为了清晰起见，我们将验证的某些部分放在了测试方法内部。
Instead of having a test method per use case, we have a text file containing the expected generated code and a optional text file containing the expected compiler messages.
和每个用例有一个测试方法不同，我们有一个文本文件包含所期望的生成代码以及包含所期望编译器消息的可选文本文件。
So, instead of letting the tool create the initial test method, I will write each method as I go.
因此，我将自己书写每一个用到的方法，不让工具生成原始的测试方法。
With the mechanics out of the way, note that I made a few design decisions in my test method.
有了这些原理之后，要注意，我在测试方法中制订了一些设计决策。
If the test method happens to take longer than 1000 milliseconds to execute, it fails.
如果执行该测试方法所花的时间多于1000毫秒，则测试失败。
Each test method has its own unique TDT.
每个测试方法都有其惟一的TDT。
Test success is indicated by completion of a test method.
测试成功通过测试方法的完成来指示。
Within that directory, we have one directory per test method, whose name exactly matches the method name.
在该目录中，我们对每个测试方法都提供了一个目录，其名称完全匹配该方法名称。
The four steps to this combination test method are: test selection, system resource utilization evaluation, kernel code coverage analysis, and final stress test evaluation.
这一组合测试方法的四个步骤是：测试选择、系统资源利用率评价、内核代码覆盖分析以及最终的压力测试评价。
The execution model is a bit strange: The test class is reinstantiated every time a test method is executed.
执行模型有点奇怪：每次执行一个测试方法的时候，都要重新实例化测试类。
The test method for this example looks like Listing 4.
此示例的测试方法类似于清单4。
I need to decide if I will have just one test method or many test methods for the different test cases.
我需要决定对不同的测试用例是使用一个测试方法还是多个测试方法。
Third, the original expectation of the test method has not changed.
第三，测试方法的原始期望并未更改。
For the first test method, you can use the information directly from the WSDL.
对于第一种测试方法，可以直接使用WSDL中的信息。
Every test method can be associated with one or more groups; once you've defined these groups, you can choose to run only certain groups of tests.
每个测试方法都可以与一个或多个组相关联，但可以选择只运行某个测试组。
If the test method does not run as anticipated, we will get an error (and a traceback describing the error).
如果测试方法没有按预期运行，我们将得到一个错误(以及描述这个错误的回溯)。
Our test method, then, looks like this
因而，我们的测试方法类似于
For example, there is a test method like the following with some simple assertions.
举例来说，下面有一个测试方法，其中有一些简单的断言。
That's why the main test method in Listing 1 USES a while loop instead of a new for loop.
这就是为什么清单1中的main测试方法使用while循环而不是一个新的for循环。
Finally, add some code in your main test method to print out and execute the generated SQL query.
最后，在main测试方法中添加一些代码，用以输出和执行所生成的SQL查询。
The business value of running scalability and performance tests comes once a business formalizes a test method that includes the following.
一旦企业形成一套包含以下几个方面的测试方法，连续的可伸缩性和性能测试就会产生企业价值。
Example of calling a unit test method.
调用单元测试方法的实例。
The following test method is used.
然后使用下面这个测试方法。
You may have several.tspec files for each test method; they will be executed in alphabetic order.
每个测试方法可以具有多个. tspec文件；它们将按字母顺序执行。
AfterTestMethod methods are executed after the execution of every test method in a class.
afterTestMethod方法在类中的每个测试方法执行之后执行。
Within the test method itself, testRunServiceAndReturnFalse(), you can see a few more changes.
在测试方法本身testRunServiceAndReturnFalse() 之内，您可以看到更多更改。
JpaTests class USES a shadowing classloader to enhance classes on the fly. It wraps each test method around a transaction and also provides a helper for declaring base Application Contexts.
AbstractJpaTests类使用了一个后台classloader在运行时增强类，它围绕事务来包装测试方法，同时提供帮助类来声明应用上下文。
To turn it on, call EasyMock.verify (mock) at the end of your test method.
要想启用它，应该在测试方法末尾调用EasyMock . verify (mock)。
BeforeTestMethod methods are executed before the execution of any test method in a class.
beforeTestMethod方法在类中的任何测试方法执行之前执行。
Finally, Rails rolls those changes back to return the database to the state that existed before the test method ran.
最后，Rails回滚这些变化，将数据库返回到测试方法运行之前的状态。
应用推荐