After you have designed test scenarios, the next step is to transform them into test scripts.
在您设计测试场景之后，接下来的一步是将它们转化为测试脚本。
Generate logs within test scripts to record time.
在测试脚本中生成记录时间的日志。
You now have three working functional test scripts.
现在你有了三个可以工作的功能测试脚本。
These can be manual steps or automated test scripts.
这些步骤可以是手工的步骤，也可以是自动的测试脚本。
Extracting user interface details from test scripts.
从测试脚本中提取用户界面细节。
Listing 5. Script updated to call your functional test scripts.
列表5更新的脚本，能调用你的功能测试脚本。
To publish manual test scripts in HTML format, follow these steps.
可以按照下面的步骤，将手动测试脚本发布成HTML 的格式。
Helper classes allow you to add functionality to your test scripts.
助手类允许您将功能添加到您的测试脚本中。
A formalized approach to elaborate the test suites and test scripts.
一种详细描述测试套件和测试脚本的形式化方法。
Support for the Jython scripting engine used to execute test scripts.
支持用于执行测试脚本的Jython脚本引擎。
Part 8: strategies for unit testing; function tests; GUI test scripts.
第8部分：单元测试策略；功能测试；GUI测试脚本。
Test provides a number of functions that automate writing test scripts.
Test提供了许多自动编写测试脚本的函数。
There's no standard way to identify expected results within test scripts.
没有一种标准方式确认在测试脚本范围中所预期的结果。
You will then be able to select the test scripts that you want to import.
然后您就能够选择您想要导入的测试脚本了。
After you import the test scripts, you can associate them with test cases.
在导入测试脚本之后，您可以将其与测试用例联系起来。
If this is not the case, test scripts need to be built over and over again.
如果不是这种情况，测试脚本就需要一次又一次地构建。
System tests ran through the entire system using the recorded test scripts.
系统测试通过使用被录制的测试脚本对整个系统进行测试。
Consider these best practices when recording and splitting your test scripts.
当您在记录和分割测试脚本时，考虑一下以下的最佳实践方式。
Search through the test scripts returned until you find the one that you added.
搜索返回的测试脚本，直到您找到您所添加的为止。
Tellurium IDE release candidate is also out to record and generate test scripts.
录制和生成测试脚本的TelluriumIDE的RC版本也已发布。
Different automated test scripts can be added in the startup profiles of the WPAR.
可以将不同的自动化测试脚本添加到WPAR的启动配置文件中。
Many testing tools are either capture-replay tools or require writing test scripts.
很多测试工具要么是捕获——重放工具，要么需要编写测试脚本。
Now the test cases can be mapped to the test scripts in the Quality Manager solution.
现在测试用例就可以映射至RationalQualityManager解决方案中的测试脚本。
I will describe in depth how to write test scripts and test cases later in this article.
在本文的后面，我将深入描述如何编写测试脚本以及测试用例。
The unit test scripts were configuration-managed so that changes to them could be tracked.
单元测试脚本是可配置管理的，以便对测试脚本的变更可以被跟踪。
You can develop test scripts based on known screen definitions in Siebel using the framework.
您可以利用这个框架基于Siebel中众所周知的屏幕定义来开发测试脚本。
The following five JMeter test plan components were used to prepare the performance test scripts.
下面五个JMeter测试计划组件用于准备性能测试脚本。
The selected JMeter components supported a common structure for all the performance test scripts.
所选择的JMeter组件针对所有的性能测试脚本提供了一个公共的结构。
By employing the automation features, users can run automated test scripts and phone interactions.
通过利用自动化特性，用户可以运行自动的测试脚本和电话交互。
应用推荐