We test your English before deciding which class to put you in.
我们测验过你的英语后再决定把你分在哪一班。
Yesterday, we had a math class test.
昨天，我们班进行了一次数学测验。
He suggested a link between class size and test results of seven-year-olds.
他建议把7岁儿童的班级大小和考试结果相关联。
Once every package has at least one test, write one test for every class.
当每个程序包都有了至少一个测试，再为每一个类编写一个测试。
Add the code shown in Listing 6 to the test class.
添加如列表6所示的代码到这个测试类中。
Paste this code into your test class and save it.
将此代码粘帖到您的测试类，并保存。
To understand how to use this, we need a test class.
为了弄清除如何使用它，我们需要写一个测试类。
You now have your test class available for execution.
您现在已经拥有了可用于执行的测试类。
The first option is to move this test class into the integration directory.
第一个选择是将此测试类转移到集成目录中。
Once you have your test class, the real action happens in your test methods.
一旦创建好测试类之后，测试方法中要有实际的动作。
Each time you save the source file, you invoke a parsing of the test class.
你每次保存这些源文件时，便调用测试类的解析。
Here is the generated test case class for our simple example.
下面是我们的简单示例所生成的测试用例类。
Listing 3 shows the dictionary application's beginning test class.
清单3显示了字典应用程序的开始测试类。
Now imagine trying to unit test a class that makes an expensive SOAP call.
现在，想像一下对发出开销较高的SOAP调用的类进行单元测试。
Optionally the test class name can be changed.
这个测试类的名称可以更改。
If a unit test crosses class boundaries, it might be a functional test.
如果单元测试跨越类边界，则它就可能是功能测试。
You wouldn't want to test every class for this new behavior.
我们不想对每一个类测试这个新行为。
Within the UML model create a test package and class.
在uml模型中，创建一个测试包和类。
The lifecycle of a test class is further illustrated in Figure 2.
图2进一步描述了测试类的生命周期。
This doesn't necessarily mean that you need to test each individual class.
这并不意味着你需要测试每一个类。
Observe in the Test pane that the project and test class values are filled in.
检查测试窗格，将看到项目和测试类值已填充。
Optionally the name of the test class can be changed.
测试类的名称也可以修改。
The ID test took only 218 ms, while the CLASS test took 19.9 seconds!
ID测试耗时218毫秒，而CLASS测试耗时19.9秒！
Running this test class produces the expected result
运行这个测试类产生的预期结果
We now we have our test class available for execution in two contexts.
现在，我们可以使测试类在以下两个上下文中执行测试。
Add these lines of code to the test behavior class.
将这些代码添加进测试行为类。
You can test this class by adding a main method.
可以添加一个main方法测试这个类。
To execute the test class, go to the J2EE perspective, Project Explorer view.
要执行测试类，请转到J2EE透视图中的ProjectExplorer视图。
Once you have an abstract aspect, create a mock target inside your test class.
有了抽象方面后，在测试类中创建一个mock目标。
I can build class stock, and I can test class stock, before I have a class market.
我可以建立一个stock类，然后在有macket类之前测试这个类。
应用推荐