人工任务的组件测试已得到改进。
在sca模块上执行组件测试。
组件测试通常是由开发人员来建立并执行。
Component tests are most commonly created and executed by developers.
必须使GUI测试区别于单元或组件测试。
You have to approach GUI testing differently from unit or component testing.
使用组件测试程序进行测试。
现在，设置装配图，以便通过接口映射组件测试关系。
Now, set up the assembly diagram to test the relationship via the interface map component.
在你设置好你的组件测试之后，下一步就是运行测试。
After you have set up your component tests, the next step is to run the tests.
如图2所示，组件测试让你能够测试下列类型的组件。
As shown in Figure 2, component test allows you to test the following types of components.
组件测试：自动为你的组件生成测试而不需要你来写代码。
Component test: Generates tests for your components without requiring you to write code.
这种类型的代码复查是组件测试和运行时分析的先决条件。
This kind of code review is a prerequisite for component testing and runtime analysis.
如之前所提到的，组件测试功能是JUnit框架的扩展。
As mentioned before, the component test facility is an extension of the JUnit framework.
这些库包括JUnit和IBM组件测试支持JAR文件。
These libraries include the JUnit and IBM component test support JAR files.
现在，对装配图进行设置以通过接口映射组件测试这个关系。
Now set up the assembly diagram to test the relationship via the interface map component.
在测试组件时，您可以选择可置换元素作为组件测试的输入。
When testing a component, you can select substitutable elements as input to a component test.
下一步你可以执行为你的那部分新代码设计的组件测试。
Next you'll execute the component tests that you have created for this new block of code.
当构建的测试延长时，通常都预示着包含了一个大型的组件测试套件。
When the testing aspect of a build is prolonged, you can generally predict that a large suite of component tests is involved.
与在组件测试中一样，现在创建了大量的框架来为这些测试提供方便。
Just as in component tests, a number of frameworks have been created to help facilitate these tests.
编写组件测试要花更长的时间，因为它们比单元测试所涉及的东西要多。
Component tests take longer to write because they're more involved than unit tests.
这是一点小小的误导，因为源代码已被变换并且现在处于组件测试项目中。
This is a little misleading since the source code has been converted and now exists under our component test project.
您可以创建组件测试项目，其中包含测试套件、执行跟踪、配置和模拟器。
You can create a component test project that holds test suites, execution traces, configurations and emulators.
正如清单3所示，现在组件测试可在执行期间依赖驻留在数据库中的特定数据。
As you can see in Listing 3, my component tests can now rely on specific data residing in the database during their execution.
通过计划安排全年中定期的架构组件测试，您可以更新和改进已经创建的文档。
By scheduling regular testing of the architecture components throughout the year, you can update and polish the documents that you have already created.
保证代码质量的另外一个重要的方面就是组件测试，这一项工作在开发中经常出现。
Another important aspect of ensuring code quality is component testing, which is an activity that occurs during development.
重要模式包括契约式设计、定义良好的接口、可组合性、可预测的行为和组件测试。
Significant patterns include design by contract, well-defined interfaces, composability, predictable behavior, and component testing.
这在组件测试中非常有用，如你可以在封装之前确认未测试代码并检查它。
This is immensely useful during component testing, as you can identify untested code and check it before it is shipped.
然后，通过使用组件测试，可以发送业务对象，并将序列化XML作为测试数据使用。
Then, using component test, you can send a business object and take the serialized XML as the test data.
既然需要进行测试，那么，让我们通过建立一个组件测试项目来建立测试用例。
Now that we have something to test, let's start creating the test cases by creating a component test project.
movieicon点击这里来查看组件测试执行，然后查看测试结果的全过程。
Movie icon Click here to see a component test being executed, and then review the results.
所以，您的单元测试套件就是名副其实的包括单元测试、组件测试和系统测试的套件。
So, it turns out that your suite of unit tests is really a suite of unit tests, component tests, and system tests.
由于组件测试处理一个架构的多个层次，所以它们经常用于处理数据库、文件系统、网络元素等。
Because component tests deal with multiple layers of an architecture, they often deal with databases, file systems, network elements, etc.
应用推荐