Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Software testing risk Management-Bug Summary Series Notes

2025-04-02 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

Shulou(Shulou.com)06/03 Report--

1. Definition:

There are too few test risks identified in the project's formal risk library.

Second, the period of occurrence

Occurs when the project has one or more test-related risks.

Third, trap performance

1. Managers' attitude towards risk minimizes negative terms.

two。 Adding risk to the risk base is often understood as a symptom of management failure, and the risk is marked as a problem or doubt.

3. The risk at the test level is not included in the project risk, otherwise it is necessary to report or take action to the executive management.

4. The identified test risks are unreasonably low probability, low severity, and low priority.

5. None of the identified risks: mitigation methods and tracking of designated people.

6. Test risks are never updated during the project.

7. Test risk is not considered in the test documentation and risk management plan.

IV. Negative consequences

1. Test risk not reported

two。 The management or the buyer is not aware of the risk of testing

3. There is no test risk management and no risk response strategy.

4. Not giving enough priority to managing test risk

Fifth, reasons

1. Managers strongly communicate their preferences, and only a few key risks can enter the project risk base.

two。 The person in charge of the risk bank has not been trained or exposed to potential test risks

3. System-level risks are overemphasized in the process of risk management, regardless of the risks of any development activities.

4. Very little evaluation of QA and QC

5. Little supervision over the testing process

VI. Suggestions

1. Prepare for

Determine the degree of management's aversion to risk and the attitude towards testing risk in the project risk library.

two。 Enable

Ensure that the person managing the risk base is aware of the risks associated with potential testing

3. Execution

Identify test-related risks and organize them into the project's official risk base.

Provide actual possibility, hazard severity and priority of test risk

4. Verification

Determine if the appropriate amount of test risk is included in the risk library

Determine whether there is adequate test process management and quality supervision and evaluation.

VII. Related Bug

Unrealistic test expectations.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report