何时使用RTB测试方法？

This is used under the below scenarios:

• RBT approach can be used whenever there is a limitation or constraint on Time, cost and resources of a project and whenever there is a need to optimize the resources.
• RBT approach is used when the program is more complex and adapts new technology and hence involves a lot of challenges.
• When the program is an R&D project and it is of first kind type and there is a number of unknowns and risks in the project.

这在以下场景中适用：

• 只要对项目的时间，成本和资源存在限制或约束，并且无论何时需要优化资源，都可以使用RBT方法。
• 当程序很复杂并采用了新技术时使用RBT方法，因此涉及许多挑战。
• 当项目是研发项目时，并且它是第一类型，项目中存在许多未知和风险。

RBT Approach Example（RBT方法示例）

Several risk based analysis approaches are used in the IT industry to overcome the risks faced by the production and its impact.

IT行业使用了几种基于风险的分析方法来克服生产所面临的风险及其影响。

Given below is one such approach:

This approach of RBT includes identifying the ‘Vital Functionalities or Key Features’ of the product and assessing the risks to which each of these functionalities get exposed to in the production and implementing appropriate mitigation measures in place to lower or mitigate the risk.

以下是一种这样的方法：

这种RBT方法包括确定产品的“重要功能或关键特征”，评估每种功能在生产中所面临的风险，并采取适当的缓解措施来降低或降低风险。

Hence the RBT approach includes testing the functionalities which have the probability of failure and highest impact on business. The types of failures could be operational or business, technical, external etc.

因此，RBT方法包括测试具有失败概率和对业务有最大影响的功能。 失败的类型可以是运营或业务，技术，外部等。

Ways to carry out Risk Analysis(进行风险分析的方法)

There is no standard process or template defined as such to carry out the risk analysis in Software testing for each and every feature of a product. Various organizations use their own approach of risk analysis methods.

没有定义标准流程或模板来在软件测试中对产品的每个功能进行风险分析。 各种组织使用自己的风险分析方法。

Risk analysis can be carried out on various project items to identify the risks and to implement RBT approach for analysis. Those items include,

• Features
• Functionalities
• User Stories
• Requirements
• Use Cases
• Test Cases

可以对各种项目进行风险分析，以识别风险并实施RBT方法进行分析。 这些项目包括:

• 特征
• 功能
• 用户故事
• 需求
• 使用用例
• 测试用例

In this case, let us focus only on Test cases to understand the Risk Based Testing approach implementation.

在这种情况下，让我们只关注测试用例，以了解基于风险的测试方法实现。

Risk Analysis Procedure(风险分析过程)

Risk analysis includes the involvement of relevant stakeholders of the program from both the ‘Technical Team and Business Team’, which includes, Owner of the Product, Product Managers, Business Analysts, Architects, Testers, and Customer Representatives.

风险分析包括来自“技术团队和业务团队”的相关利益相关者的参与，其中包括产品所有者，产品经理，业务分析师，设计师，测试人员和客户代表。

Brainstorming session involving these stakeholders would be organized to carry out the discussion to identify the importance of each feature of a product and prioritize them based on the risk of failure and its impact to the end users in production.

将组织这些利益相关者的头脑风暴会议，以进行讨论，来确定产品的每个功能的重要性，并根据故障风险及其对最终用户的影响对其进行优先排序。

Various ‘Project Documents’ such as Requirements Document, Technical Specification Documents, Architecture and Design Documents, Business Process Document, Use Case Document etc., will become the input for the brainstorming session.

各种“项目文档”，如需求文档，技术规范文档，架构和设计文档，业务流程文档，用例文档等，将成为头脑风暴会议的输入。

Stakeholder’s knowledge about the product and the existing product in the market will also be an input factor for the discussion.

利益相关者对产品和市场上现有产品的了解也将成为讨论的输入因素。

Few other sources of inputs can also include,

1. To gather inputs on most used functionality.
2. Inputs from consulting a domain expert.
3. Data from the previous version of the product or similar product in the market.

一些其他的灵感来源也可以包括：

1、收集最常用功能的输入。
2、咨询领域专家的意见。
3、来自先前版本的产品或市场上的类似产品的数据。

During the brainstorming session, the risks pertaining to each of these features are identified. The types of risks could be an operation, technical or business related. The tests and scenarios related to them are weighted and risk values are assessed based on the likelihood of risk occurrence and impact of the risk.

在头脑风暴会议期间，确定了与这些特征中的每一个相关的风险。 风险类型可以是操作，技术或业务相关。 对与其相关的测试和情景进行加权，并根据风险发生的可能性和风险的影响评估风险值。

The ‘Likelihood of risk occurrence’ can be due to:

1. Poor understanding of the feature by the product development team.
2. Improper architecture and design.
3. Insufficient time to design.
4. Incompetency of the team.
5. Inadequate resources – people, tools, and technology.

“风险发生的可能性”可能是由于：

1、产品开发团队对该功能的理解不足。
2、不正确的架构和设计。
3、设计时间不足。
4、团队的能力不足。
5、资源不足 - 人员，工具和技术。

The ‘Impact of the risk’ is the effect of failure to the users and business if it occurs. The impact could be,

1. Cost impact, resulting in a loss.
2. Business impact resulting in losing business or losing market share, Law proceedings, Loss of license.
3. Quality impact, resulting in substandard or incompetent product release.
4. Bad user experience, resulting in dissatisfied and loss of a customer.

“风险的影响”是指发生故障对用户和业务的影响。 影响可能是：

1、成本影响，导致损失。
2、业务影响导致业务损失或失去市场份额，法律诉讼，许可证丢失。
3、质量影响，导致产品不合格或缺失。
4、糟糕的用户体验，导致客户不满意和流失。

The focus area of assessing the risk of a feature or product can be,

• Area of Business criticality of the functionality.
• Most used features and important functionality.
• Defect prone areas
• Functionality bearing the safety and security impact.
• Area of Complex Design and Architecture.
• Changes made from previous versions.

评估功能或产品风险的重点方面可以是：

• 业务领域的功能重要性。
• 最常用的功能和重要功能。
• 缺陷易发区域。
• 可承受安全的功能和安全的影响。
• 复杂设计和设计领域。
• 来自以前版本的更改。

最后

以上就是慈祥绿茶为你收集整理的基于风险的测试终极指南：软件测试中的风险管理(二)何时使用RTB测试方法？Ways to carry out Risk Analysis(进行风险分析的方法)Risk Analysis Procedure(风险分析过程)的全部内容，希望文章能够帮你解决基于风险的测试终极指南：软件测试中的风险管理(二)何时使用RTB测试方法？Ways to carry out Risk Analysis(进行风险分析的方法)Risk Analysis Procedure(风险分析过程)所遇到的程序开发问题。

如果觉得靠谱客网站的内容还不错，欢迎将靠谱客网站推荐给程序员好友。