全部

1·This type of testing is called scenario testing, task-based testing, or use-case testing.

这类测试称为场景测试、基于任务的测试，或使用用例测试。

2·Features like artefact categorization, search, collaboration and scenario testing before deployment are supported.

支持对交付件的分类、检索、协作和部署前的场景测试等特性。

3·Pressure testing is a tool to test possible actions under a specific pressure, including sensitivity testing and scenario testing.

压力测试是检测特定压力情景下可能发生情形的一项工具，包括敏感性测试和情景测试。

4·If your product isn't meant to be automated in the customer's environment, then you want a combination of automation, AD hoc, exploratory, and customer scenario testing.

如果你的产品不打算在客户环境中实现自动化，那么你需要将自动化的，特殊化的，探查的以及客户场景的测试进行合并。

5·We will use this knowledge later when testing the scenario.

稍后在测试该场景时，我们将使用这些知识。

6·All these issues have brought challenges to governance in a testing scenario.

所有这些问题给测试场景中的治理带来了挑战。

7·Documentation procedures for simple tasks, such as starting a server, can seem trivial at first but can be a source of confidence when testing a disaster scenario.

用于诸如启动服务器等简单任务的文档过程起初好像微不足道，但是在测试灾难场景时却可能是信心的来源。

8·If one considers the flow of a scenario through testing, we can construct a set of checkpoints, an example of which is shown in Table 1.

如果有人考虑通过测试的场景的流程，我们可以考虑构造一组检查点，表1中所显示的一个实例。

9·The scenario includes configuring a test server and testing an EAB component in the development environment.

这种情形涉及了配置测试服务器以及在开发环境中测试EAB组件。

10·The most likely scenario for using the deployment descriptor username and password is during initial development testing.

使用部署描述符用户名和密码的最可能场景是在初始化开发测试过程中。