所以，将这个用例的测试目标设置为每小时 12738 个事务。
The test target of this case was set at 12738 transactions per hour.
其次，团队应该始终执行用例的静态测试。
Secondly, teams should always perform static testing of the use case.
用例的静态测试可以由检查表驱动，安全的各种水平也应该包含测试人员。
Static testing of the use case can be driven by a checklist, and levels of scrutiny should involve testers.
第二步，将服务用例编写为服务测试。
用例在测试估计领域提供了令人兴奋的机会。
Use cases provide exciting opportunities in the area of test sizing.
制定测试计划和用例。
开发体现服务用例的服务测试。
验收测试则由用例的最高形式触发的。
Acceptance tests are motivated by the highest form of the use case.
仅当服务恰当地实现了用例时，测试才能通过。
The test will only pass when the services properly implement the use cases.
用例和测试。
有很多静态测试项目用例的方法。
There are multiple approaches to static testing of a project's use cases.
用例对测试组织的利益。
一开始我要选择两个用例进行测试。
基于商业成果的结果评估(根据用例场景测试系统)。
Assessment of results based on business accomplishments (System tested against Use Case Scenarios).
在设置了场景和测试用例之间的追踪关系后，我们可以创建一个显示从用例到测试用例全部追踪方法的追踪树。
After setting the traceability between scenarios and test cases, we can create a traceability tree that shows traceability all the way from use cases to the test cases.
通过追踪从用例到业务用例、特性需求、测试，或者甚至其它用例，你可以更容易地衡量相关需求的变化所带来的影响，并验证覆盖率。
By tracing use cases to business requirements, feature-level requirements, tests, or even other use cases you can more easily measure the impact of change on related requirements and verify coverage.
当执行基于用例的测试时，最明显的技术是过程循环测试(或规则测试)。
When performing testing based on use cases, the most obvious technique is the process cycle test (or algorithm test).
要为测试用例设置吞吐量基准，如果在以前的发行版中已经对这一用例做过测试，我们常常使用以前的结果作为我们的基准。
To set a throughput baseline for a test case, and if the case has been tested in a previous release, we often use its previous result as our baseline.
对于验收测试，当被适当地执行时，用例缩小了测试人员概念化和用户目标现实之间的距离。
For acceptance testing, when properly implemented, use cases shorten the gap between the tester's conceptualization and the reality of user goals.
您可以通过检查并计算用例描述中涉及到的用例事务来检查并计算用例事务，来进行测试。
You can test for "sameness of size" by detecting and counting the use case transactions that are involved in your use case specifications.
这种处理用例检验的方法可以变化，但是很明显，这些用例在测试用例的创建种有重要的价值，团队必须从形式上关注这些用例的质量。
The approach to use case review may vary, but clearly, teams must give formal attention to the quality of the use cases if they are to be of value in test case creation.
基于这些用例，测试可以在一个受限层次上进行，因为用例只描述执行者和系统的交互。
Based on use cases, testing can progress on a limited level since use cases only describe the interactions between actors and the system.
用这种方法，每个用例都要测试。
用例实现对测试组织最大的影响是在测试用例的创建过程中。
The greatest impact use case implementation can have on a test organization is in test case creation.
通常，编写完业务需求后，团队成员会进行深入的探讨，建立起具体的用例，由这些用例驱动测试用例、单元测试和最终代码的实现。
Typically the Business requirement is written and the team will drill down to flesh out the use cases that will drive the tests cases, the unit tests and ultimately the implementation code.
用例驱动测试过程，但是它们不直接处理各种类型的测试用例。
Use cases drive the testing process, but they cannot directly address many types of tests cases.
你也可以重用每个构件，来组合成多种较大的验证一个应用软件用例的测试。
You can also reuse each component to assemble a variety of larger tests that validate an application use case.
一旦你选择了下次迭代将被实现的用例，你应当验证追踪到用例的测试需求，以确保所有的功能都能得到测试。
Once you have selected the use cases to be implemented in the next iteration, you should verify that test requirements are traced to use cases ensuring that all the functionality will be tested.
测试人员直接根据说明用例的功能需求创建测试脚本。
The tester creates test scripts directly from the functional requirements that illustrate the use case.
测试团队然后采用这些用例，构建测试脚本并执行测试计划人员制定的测试计划。
The test team then takes the use cases, builds the test scripts, and executes the test plans developed by the test planner.
应用推荐