You now have your test class available for execution.
您现在已经拥有了可用于执行的测试类。
Optionally the test class name can be changed.
这个测试类的名称可以更改。
Listing 3 shows the dictionary application's beginning test class.
清单3显示了字典应用程序的开始测试类。
Add the code shown in Listing 6 to the test class.
添加如列表6所示的代码到这个测试类中。
The first option is to move this test class into the integration directory.
第一个选择是将此测试类转移到集成目录中。
Optionally the name of the test class can be changed.
测试类的名称也可以修改。
The lifecycle of a test class is further illustrated in Figure 2.
图2进一步描述了测试类的生命周期。
To execute the test class, go to the J2EE perspective, Project Explorer view.
要执行测试类，请转到J2EE透视图中的ProjectExplorer视图。
Here is the generated test case class for our simple example.
下面是我们的简单示例所生成的测试用例类。
You wouldn't want to test every class for this new behavior.
我们不想对每一个类测试这个新行为。
Now imagine trying to unit test a class that makes an expensive SOAP call.
现在，想像一下对发出开销较高的SOAP调用的类进行单元测试。
Add these lines of code to the test behavior class.
将这些代码添加进测试行为类。
You can test this class by adding a main method.
可以添加一个main方法测试这个类。
Within the UML model create a test package and class.
在uml模型中，创建一个测试包和类。
This doesn't necessarily mean that you need to test each individual class.
这并不意味着你需要测试每一个类。
Writing a unit test for a Stack class is straightforward.
可以很直观地写出对堆栈类的单元测试。
You also use this class to run test packages.
您也可以用这个类来运行测试包。
Write the unit test before writing code for class it tests.
首先编写单元测试，然后再编写要测试的类代码。
Every test case must extend from this class.
每个测试用例都必须是从这个类扩展而来。
To keep the code simple, I put the class and the test code in one file.
为了保持代码简单，我把类和测试代码放在一个文件中。
Look at Listing 10, which defines a test suite for your string class.
清单10为字符串类定义一个测试套件。
Generating a test for a specific function or class.
为特定的函数或类生成测试。
Having coded the RolloverIcon class, we now need to test it.
编写完rollovericon类的代码后，现在我们需要测试它。
Although hit was difficult, the class passed the test with excellent marks.
虽然难度很高，这个班级还是以高分通过了测试。
The file contains the necessary JMS protocol handler class for our test application.
这个文件包含测试应用程序必需的JMS协议处理类。
Observe in the Test pane that the project and test class values are filled in.
检查测试窗格，将看到项目和测试类值已填充。
Once you have an abstract aspect, create a mock target inside your test class.
有了抽象方面后，在测试类中创建一个mock目标。
If a unit test crosses class boundaries, it might be a functional test.
如果单元测试跨越类边界，则它就可能是功能测试。
Once every package has at least one test, write one test for every class.
当每个程序包都有了至少一个测试，再为每一个类编写一个测试。
Once every class has at least one test, write one test for every method.
当每个类都有了至少一个测试，再为每一个方法编写一个测试。
应用推荐