Add test scripts and all test scripts listed.
添加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.
从测试脚本中提取用户界面细节。
Test suite: Enables sequential execution of 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.
一种详细描述测试套件和测试脚本的形式化方法。
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.
系统测试通过使用被录制的测试脚本对整个系统进行测试。
Testers resolve the task by delivering the finished test scripts to the server.
测试员通过向服务器交付完成的测试脚本来终结任务。
Search through the test scripts returned until you find the one that you added.
搜索返回的测试脚本，直到您找到您所添加的为止。
Testers can record and play back on such applications and generate test scripts.
测试人员可以记录并作用于这样的应用程序上，从而产生测试脚本。
We'll record three functional test scripts that we'll use for regression testing.
我们将记录三个功能测试脚本并用它们组成回归测试。
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.
很多测试工具要么是捕获——重放工具，要么需要编写测试脚本。
File locations are records that hold paths to external files, including test scripts.
文件位置就是保持外部文件路径的记录，其中包括测试脚本。
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.
单元测试脚本是可配置管理的，以便对测试脚本的变更可以被跟踪。
After you have designed test scenarios, the next step is to transform them into test scripts.
在您设计测试场景之后，接下来的一步是将它们转化为测试脚本。
It's hard or impossible to reuse test script lines or groups of lines in different test scripts.
很难或者基本不可能在不同的测试脚本中重用测试脚本基线，或者基线组。
By employing the automation features, users can run automated test scripts and phone interactions.
通过利用自动化特性，用户可以运行自动的测试脚本和电话交互。
This is an oversimplified example; our actual tests involved much more comprehensive test scripts.
这是一个非常简单的例子；我们实际的测试会包括更加复杂的测试脚本。
We will begin with creating two sample test scripts, where one is manual and the other is automated.
开始时我们需要创建两个范例测试脚本，一个是手动的，另外一个是自动的。
You need to use two migration files, one to migrate test scripts and the other to migrate test cases.
您需要使用两个迁移文件，一个去迁移测试脚本，另一个去迁移测试用例。
应用推荐