从测试脚本中提取用户界面细节。
缺陷清单标识遇到了问题的测试脚本。
The defect ticket identifies the test script that encountered the problem.
现在你有了三个可以工作的功能测试脚本。
测试集：能够对测试脚本执行连续的执行。
然后您就能够选择您想要导入的测试脚本了。
You will then be able to select the test scripts that you want to import.
出于测试目的，我创建了一个简单的测试脚本。
然后，IDE将运行为项目指定的测试脚本。
The IDE then runs the test script designated for the project.
此时，您只是测试脚本，确保它返回合理的数据。
At this point, you are just testing the script to make sure that it returns sensible data.
搜索返回的测试脚本，直到您找到您所添加的为止。
Search through the test scripts returned until you find the one that you added.
熟悉录制和回放测试脚本，并理解测试脚本的内容。
Familiarity with recording and playing back test scripts and an understanding of the content of test scripts.
我们将记录三个功能测试脚本并用它们组成回归测试。
We'll record three functional test scripts that we'll use for regression testing.
助手类允许您将功能添加到您的测试脚本中。
Helper classes allow you to add functionality to your test scripts.
在导入测试脚本之后，您可以将其与测试用例联系起来。
After you import the test scripts, you can associate them with test cases.
图5显示了测试脚本回放期间功能测试组件的交互作用。
Figure 5 shows the interaction of the functional test components during playback of the test script.
输入测试脚本的名字；默认条件下，通知类型会设置成手动。
Enter the name of the test script; by default, the notice type is set to manual.
测试脚本是以已定义的格式打印到STDOUT的任何程序。
A test script is any program that prints to STDOUT in a defined format.
文件位置就是保持外部文件路径的记录，其中包括测试脚本。
File locations are records that hold paths to external files, including test scripts.
我们也意识到有时我们更新了测试脚本但没有修改测试计划。
We also realized that sometimes we'd updated the test script without modifying the test plan.
改变现有测试界面细节不再需要测试人员修改每个测试脚本。
Change to existing user interface details no longer requires the tester to revise each test script.
只要测试实例依旧完整的话，我们就无需重新捕获测试脚本。
There is no need to re-capture the test script as long as the test cases remains intact.
在本文的后面，我将深入描述如何编写测试脚本以及测试用例。
I will describe in depth how to write test scripts and test cases later in this article.
当您的测试完成时，请停止记录，随后测试脚本将会自动产生。
When your test scenario has completed, stop the recording, and the test script will be generated.
测试员通过向服务器交付完成的测试脚本来终结任务。
Testers resolve the task by delivering the finished test scripts to the server.
测试人员直接根据说明用例的功能需求创建测试脚本。
The tester creates test scripts directly from the functional requirements that illustrate the use case.
需求、软件设计，甚至测试脚本与代码比较有相对短的预期寿命。
Requirements, software designs and even test scripts have relatively short life expectancies compared to code.
通过利用自动化特性，用户可以运行自动的测试脚本和电话交互。
By employing the automation features, users can run automated test scripts and phone interactions.
很多测试工具要么是捕获——重放工具，要么需要编写测试脚本。
Many testing tools are either capture-replay tools or require writing test scripts.
测试执行通过将测试脚本的顺序集合成测试套件来运行这些测试。
Test execution entails running the tests by assembling sequences of test scripts into a suite of tests.
没有一种标准方式确认在测试脚本范围中所预期的结果。
There's no standard way to identify expected results within test scripts.
在将测试脚本加入MANIFEST后，MANIFEST如下。
After the test script has been added to the MANIFEST, it looks as follows.
应用推荐