详细测试计划原则现在也整合到了SOMA[1]当前版本之中，SOMA是一种IBM方法。
Detailed test planning guidelines are also now integrated within current releases of SOMA [1], an IBM methodology.
这种复杂性导致了即使是经过详细测试的系统，也会在部署后出现性能和功能达不到要求的情况。
As a result, even systems that have been thoroughly tested can fail to provide adequate performance and functionality post-deployment.
所有这些，再加上加州作为技术创新之乡的声誉，使这里成为开发和测试旨在详细监测污染的系统的理想之地。
All of which, combined with California's reputation as the home of technological innovation, makes the place ideal for developing and testing systems designed to monitor pollution in detail.
你可以划分详细设计、实现和测试阶段到三个迭代中，每个迭代瞄准实现九个子系统中的三个。
You can divide the detailed design, implementation and test phase into three iterations, each one aiming at implementing three of the nine subsystems.
划分详细设计、实现和测试阶段到不同的迭代中。
Divide the detailed design, implementation and test phases into iterations.
步骤2：划分详细设计、实现和测试阶段到不同的迭代中。
Step 2: Divide the detailed design, implementation and test phases into iterations.
功能验证测试通常被认为是针对详细需求以及外部和内部设计文档的功能组成的测试。
The function Verification test is typically considered to be the testing of functional components against Detailed Requirements as well as External and Internal Design documents.
并且，与其它系统开发方法比较，RUP提供了详细的测试指导。
And, compared to other system development methods, RUP provides detailed test instructions.
在您设计出任务列表后，请记住将必须执行的非编码工作列入其中，例如详细撰写设计文档、测试或只是确定一些新任务。
As you work out your task list, remember to include the non-coding work that you have to do, such as writing up design documentation, testing, or just figuring out something new.
这需要组织和维持测试项目的详细目录，以及用来执行测试的各类事物。
This requires organizing and maintaining an inventory of items to test, along with the various things used to perform the testing.
IRAD提供了可以帮助你决定如何优化测试中的组件的详细静态度量。
IRAD offers detailed static metrics on the component under test that can help you decide how to prioritize your tests.
在随后的计划中，您可以通过向每一个测试用例添加一个加权值，来提供一份详细的关于测试执行效果的估计。
Later in the plan, you can provide a more detailed estimate of the test execution effort by adding a weight value to each test case.
如果测试失败，用户就可以查看详细的日志来找出测试在哪里出现问题，这样用户可以很容易地准确地确定需要在哪里进行变更。
If a test fails, the user can view a detailed log to find out where a test misfired, so he can easily determine exactly where changes need to be made.
使用在屏幕顶部附近的绿色菜单栏中提供的选项，我们能够选择查看更加详细的测试报告，比如，页面访问、CPU负载和平均负载时间。
Using the options provided in the green menu bar near the top of the screen, we could have chosen to see more detailed reports covering, for example, page access, CPU load, and average load times.
如果出现意外情况，并且无论您计划多么周密、测试多么详细，该情况都仍然出现，则此时也可能需要执行回滚。
A rollback may also be necessitated when the unexpected occurs, and no matter how much planning and how much testing you might have done, the unexpected is bound to happen.
测试管理是详细说明目标、用于测量这些目标的方法以及将如何收集这些数据的地方。
Test management is where the goals, the metrics used to measure such goals, and how the data for them will be collected are defined.
我们将对此场景使用自顶向下的方法，即先执行测试，然后分析发生的处理，最后详细了解测试步骤的规范。
We will follow a top-down approach to this scenario, first executing the test, then analysing the processing that occurred, and then, finally, looking in detail at the specification of the test step.
您可能会发现此输出内容相当详细；您可以修改测试框架，使之更简洁，以供日常使用。
You might find this output to be rather verbose; you can modify the test framework to be more terse for day-to-day use.
但我们没办法进行更详细的测试。你可以看看文末提供的通话中的照片。
No, we weren't able to extensively test it, but you can see below for in-call screens and the like.
测试和QA计划：详细说明测试和 QA 计划，并在其中包括测试用例。
Testing and QA plan: Details the testing and QA plans and includes test cases.
详细的测试执行报告以及与其相关的指标。
Detailed test execution reports and metrics associated with them.
有关这些额外测试的更多详细内容在TMap方法中可以得到。
More specific details about these additional tests are available within the TMap method itself.
详细的节点测试语法和语义参见参考资料中的XPath2规范。
The detailed syntax and semantics of the node tests can be found in the XPath 2 specification in Resources.
我们在后面将详细解释如何使用IntegrationDeveloper测试客户端。
We will explain the details of how to use the Integration Developer test client later in this article.
利用这个向导，您就可以为以后测试对比的运行详细指定TestObject和数据。
Using that wizard, you then specify the TestObject and the baseline data for subsequent runs to test against.
测试用例的范畴，像标签那样，让您能够为更详细的报告将测试用例拆分。
Test case categories, which, like tags, enable you to partition your test cases for more detailed reporting.
FunctionalTester工具并没有提供一种详细的测试SAPGUI的配置向导。
The Functional Tester tool does not provide a specific wizard for configuring the SAP GUI for testing.
应该执行一些简单的连通性测试，以确认指南中详细讲述的集成安装。
Certain simple connectivity tests should be performed to verify the integrated installation as detailed in the guide.
表1展示了所测试系统的详细配置信息。
Table 1 shows the configuration details of the system tested.
取决于测试思想的详细程度，这种映射可以在准备阶段中的测试技术选择中或在规格说明阶段的测试用例规格说明中发现。
Depending on the level of detail of test ideas a mapping can be found in the choice of test techniques in the Preparation phase or in the specification of test cases in the specification phase.
应用推荐