Add the text file to list the testCase classes.
添加文本文件以列出testcase类。
The TestCase class is the one you'll use the most.
testcase类是您将最常使用的类。
Repeat Steps 1-4 to create Tasks and TestCase folders too.
重复1 - 4的步骤，创建Tasks和TestCase文件夹。
It doesn't extend TestCase, nor does it have any test cases defined.
它既没有扩展TestCase，也没有定义任何测试用例。
The TestCase class still works, but you're no longer required to extend it.
TestCase类仍然可以工作，但是您不再需要扩展它了。
For each test case. basically you need to extend your test class from TestCase.
对于每个案例来说，您都需要从TestCase扩展您的测试类。
It's a TestCase that exposes the public static TestSuite suite method signature.
它是一个公开publicstaticTestSuitesuite方法签名的TestCase。
You just write a test class (TC_Person in this example) that subclasses TestCase.
您只是写了一个测试类(在该示例是tC _ Person)，它是TestCase的子类。
The files should be sent to the IBM testcase server using a unique filename for each file uploaded.
对于上载的每个文件，都应该使用唯一文件名将这些文件发送到IBMTestcase服务器。
Unlike the previous example of running a single TestCase, the suite runs as a stand-alone application.
与前面运行单一testcase的例子不同，套件作为单独的应用程序运行。
Hence, any implementing class of TestCase can refer to an assert method within its own defined methods.
因此，任何TestCase实现类都可以在它自己的已定义方法中引用断言方法。
Listing 3 shows part of the code of the ApplicationUtilTest object that represents the TestCase object.
清单3显示了表示TestCase对象的ApplicationUtilTest对象的部分代码。
The typical JUnit programming model creates a test class by extending the TestCase class provided by JUnit.
典型的JUnit编程模型通过扩展JUnit提供的testcase类创建测试类。
Therefore, all those assert methods are now instance methods on TestCase, as you can see back in Listing 17.
因此，这些断言方法现在都是TestCase上的实例方法，如清单17 所示。
While declaring void limits the reach of the testCase() pointcut, it reduces complexity and increases protection.
虽然声明void限制了testCase()切入点的应用范围，但是这样降低了复杂性，增强了安全性。
You now have a concrete JUnit TestCase class that can be treated as if the suite composite were statically defined.
现在就有了一个具体的JUnitTestCase类，可以像静态定义的包那样处理它。
In fact, the GWT development team created a helper class dubbed GWTTestCase that extends from JUnit's 3.8.1 TestCase.
事实上，GWT开发小组还为此创建了一个帮助器类GWTTestCase，扩展自JUnit的3.8.1 TestCase。
Add a method to TestCase that will test the deposit method on Account. The test class should now look like Listing 1.
向TestCase添加一种方法将测试Account的deposit方法。
Extending JUnit's TestCase class to add additional features is a common technique utilized in virtually every JUnit extension.
扩展JUnit的testcase类，加入附加特性，实际上是每个JUnit扩展通常采用的技术。
Using Assert.assert{something}(..) ties TestCase to TestResult more deeply and hides the flexibility of a collecting parameter.
可以使用Assert.assert{something}(..) 将TestCase 绑到TestResult 上，进一步限制收集参数的灵活性。
The first option is to write normal JUnit test cases just as you've been doing all along by extending JUnit's commendable TestCase.
第一个选择是编写普通的JUnit测试用例，就像以前一直做的那样，扩展JUnit令人称赞的TestCase。
TestCase extends assert, which defines a number of useful static assert {something} (..) methods for checking and logging failures.
TestCase扩展了assert，后者定义了一些有用的static assert {something}(. .)方法，以检查和记录失效。
The first article in this series has already addressed why TestCase class-based testing is often not necessary in the modern world.
本系列的第一篇文章已经讨论过基于 TestCase 类的测试在现代环境中为什么常常是不必要的。
PortletUnit USES JUnit to provide the outline of a testing framework (such as creation of TestCase and TestSuite using assertions).
portletUnit使用JUnit提供测试框架轮廓(比如使用断言创建TestCase和TestSuite)。
The usual programming model with JUnit version 3.8 is to create a test class that extends one of the TestCase classes provided by JUnit.
JUnit版本3.8的常见编程模型是创建测试类，它扩展了JUnit提供的一个testcase类。
This module defines a cornucopia of assertion methods, but rather than being extended, Ruby's TestCase class includes the assertion as a mix-in.
这个模块定义了许多断言方法，但是Ruby不对这个模块进行扩展，Ruby的testcase类以mix - in的形式包含assertion。
Some might manage their own data, as TestCase does; others might benefit from dependency inversion, where their configuration is established extrinsically.
有些可能管理自己的数据，如TestCase；有些可能得益于依赖性倒置(dependencyinversion)，在外部建立配置。
Experienced users of unittest might try to argue that the above example should use the testing methods that my new TruthTest class has inherited from TestCase.
有使用unittest经验的用户可能认为，上面的示例应该使用truthtest类从testcase类继承的测试方法。
To enable harness developers to specify different test cases, both the pointcut and method are abstract. For example, here is how I could adapt this to TestCase
为了让装置开发人员指定不同的测试用例，切入点和方法都是抽象的。
After the require statement, a class declaration stating that this class is a subclass of Test: : Unit: : TestCase must be added (as shown in below in Listing 6).
在require语句后面，添加一个类声明，指出这个类是Test： Unit：TestCase的子类(见清单6)。
应用推荐