使用各种测试模块来构筑测试场景。
测试模块(而不是组件)时，将禁用模拟。
When testing modules (as opposed to components), emulation is disabled.
测试变量功能会促进测试模块之间数据的交换。
The test variable functionality facilitates the exchange of data between the test modules.
这就是为什么需要记录测试模块的附件的原因之一。
This is one of the reasons why documenting your test module's dependencies is necessary.
通过重新组织和合并测试模块来构建更大的用户场景。
Build bigger user scenarios by reorganizing and combining test modules.
创建一个JUnitEE测试模块，并对它进行配置。
首先，将测试模块添加到服务器，并确保服务器已启动。
First, add the test module to the server and make sure the server is started.
最后，测试模块需要访问我们正在测试的模块的接口库。
Finally, our test module will need access to the interface library of the module we are testing.
VA02测试模块删除了VA01测试模块创建的顺序。
The VA02 test module deletes the orders that the VA01 test module creates.
从单个记录那里获得测试模块，同时原始的测试丝毫未变。
Derive test modules from a single recording, while keeping the original test intact.
图13显示了用于建模工作负荷场景的各种测试模块的范例。
Figure 13 shows an example of various test modules being used to model a workload scenario.
测试模块：选择要测试模块中的一个或多个组件并测试多个模块。
Testing modules: selecting one or more components in a module to test and testing multiple modules.
当您在使用测试模块建模工作负荷场景时，要一直维护测试的通用结构。
Always maintain the general structure of a test when modeling your workload scenario using the test modules.
l _ MailService(它提供对我们要测试模块的访问)。
L_MailService (this giving access to the module we are testing).
我觉得这个测试模块完全可以持续两年的时间，而且大气还不出什么问题。
I felt that the test module could have gone on for the full two years and kept its atmosphere right.
本文讨论下一步，介绍框架在找到测试模块之后如何发现其中的待测试项。
This article takes the next step and asks what the frameworks do when they then introspect a test module to discover what tests live inside of it.
让自己遵从python的标准测试模块规定的方法学是良好的软件实践。
Committing yourself to the methodology provided by Python's standard testing modules is good software practice.
这些测试变量会自动生成和设置，同时分割测试以在测试模块之间创建联系。
They are test variables automatically generated and set while splitting a test to create links among the test modules.
图6显示了一些测试模块（A到D），它们用于创建不同的测试场景。
Figure 6 shows an example of various test modules (A through D) being used to create different test scenarios.
要测试模块，您可以选择组件的操作，输入输入值，然后单击Continue。
To test the module, you select an operation of a component, enter input values, and then click Continue.
在您识别想要联系在一起的测试模块之后，接下来的一步是声明变量，并分配它们。
After you have identified the test modules that you want to link together, the next step is declaring variables and assigning them accordingly.
创建测试模块脚本然后记录和回放脚本通常会有较高的成本，但是维护成本更加便宜。
There is typically a higher cost to create test modular scripts then record and playback scripts, but the maintenance costs are cheaper.
图2显示了一个范例，其中有三个不同的测试模块来自于单个SAP测试记录的测试。
Figure 2 shows an example where three different test modules are derived from a test from a single SAP test recording.
与之类似，通过删除或者禁止特定场景所不需要的测试模块，可以使模块变得小一点。
Likewise, it can be made smaller by removing or disabling the test modules that are not needed for a particular scenario.
图12显示了第二个测试模块(VA02)，它使用与VA01测试模块相同的名字。
Figure 12 shows a second test module (VA02) that is using a variable with the same name as the VA01 test module.
下一步，创建测试模块与包含有要映射的数据类型和要测试的数据映射的库之间的关联。
Next, create the association between the test module and the library that contains the data types to map and the data maps to test.
测试模块包含了Login，Createorder以及Logout测试。
The test modules include Login, Create order, and Logout tests.
当您完成开发和定制测试模块时，您就可以组织和合并各种测试模块，以评价工作负荷场景。
When you are finished with developing and customizing your test modules, you can organize and combine various test modules together to emulate a workload scenario.
测试模块可以交互性地使用，以构筑更大或者更小的用户场景，这取决于测试的目的是什么。
The test modules can be used interchangeably to construct bigger or smaller user scenarios, depending on the test objectives.
正如在图2及图4中所描述的那样，您可以在记录之后，以及记录期间从测试中创建测试模块。
As depicted in Figure 2 and Figure 4, you can create test modules from tests after and during recording.
应用推荐