这种最佳的操作允许您基于测试用例的复杂性、风险以及功能性区域来安排它们的优先级，来建立关于测试将要持续多久的质量估计。
This best practice allows you to prioritize test cases based on their complexity, risk, and functional area, which will create a quality estimate about how long the testing will take.
在你的测试计划解决中合并基于风险和客户分析将产生一个更加实际和实用的测试计划。
Incorporating both risk - and customer-based analysis into your test plan solution will yield a more practical and pragmatic test plan.
当在基于静态的优先级团队执行识别的测试时，风险区域也会被识别。
While executing tests identified in the static-based prioritized group, risk areas are identified.
因此，测试过程的提前管理并应用一种基于风险的方法，如TMap所描述的，是必须的。
Proactive management of the test process and applying a risk-based approach, as TMap describes, is therefore mandatory.
另外一个差异是，TMap测试策略基于风险、质量特性、系统部分和必需的测试技术。
Another difference is that the TMap test strategy is based on risks, quality characteristics, system parts, and required test techniques.
降低基于复用由现有核心业务系统移植来的已证实且测试了的功能的风险。
Lowering the risks based on the reuse of proven, tested functionality migrated from existing core business systems.
本节将迅速查看一下选择数据进行测试的5种不同方式：基于风险、基于需求、基于可用性、使用生产数据，或者随机使用产生的数据。
This section will quickly examine five different ways to select data for testing: based on risk, based on requirements, based on availability, using production data, or using randomly generated data.
软件系统的最小化风险，基于需求的测试 (ranTEST).
Risk-minimising, requirements-based testing of software systems (ranTEST).
在介绍了基于风险测试的基本原理后，通过简化的测试模型讨论了基于风险测试的方法在软件揭错能力上的改善。
After specifying theory of risk-based testing, this paper gives a simple analysis model to explore the improvement of risk-based testing on software testing fault-detecting ability.
基于产品风险，确定要测试和不需要测试的功能和项目。
The items and features to be tested, and not to be tested, are identified based on the product risks.
施工阶段风险的分段评估和基于现场测试技术的评估。
During the construction phase, firstly, establishing a suitable risk assessment index system.
施工阶段风险的分段评估和基于现场测试技术的评估。
During the construction phase, firstly, establishing a suitable risk assessment index system.
应用推荐