How to classify the found defects in a strict hierarchy

Source: Internet
Author: User

For how to divide the grade of the defect, the test data are detailed in detail, as long as the classics can answer the question, and to be divided into 100 points. However, how many people can recite, as long as the back is not down, it means that the answer exists only in theory and can not be used in combat. We need to understand that only an understanding of the defect classification is feasible, and that is exactly what we need.

Before we divide the defect ranks, we need to think about why we need to divide the hierarchy. Unfortunately, Baidu I did not find the relevant answer. My point is that the grade of the defect is used to assess the potential impact of the defect on software use, one of the direct basis for software quality evaluation, the test of the main indicators, the main reference to repair priority. The more the impact of software use, the lower the quality score, the more need to develop the defects as soon as possible to modify its severity level will be higher, the same defect severity rating is based on these conditions.

Back to the question, my question is: Does the hierarchy need to be done closely? It might be an answer, of course, it's a serious job. The implementation of the law also five, there is no strict grading criteria and how to decide the level of defects, no standards are not implemented. But this is not the law enforcement, not so high requirements, besides the law is also rational, sentiment, and the workplace is the first after the law at the same time also talk about feelings, encountered a defect in the pre-defined level of the standard does not exist, what will you do? It is estimated that you will not improve the standard, but I think a certain level more "rationale", because the "reason" even let the test staff even the grading standards can not remember, talk about the strict.

In different defect tools, the classification of defects is not the same. The levels in QC are level 4, some open source tools have 5 levels, and even some companies have 7 levels, what is the basis for different levels to define in advance? What was the original intention of setting these levels? This is a priority issue that we need to consider. After this question is clear, the rest is to implement how to determine the defect level, my point of view: In the heart of a reason, the law in the belly when the desk, mouth appropriate Valentine, as long as reasonable, all harmony. to be tight, first set the level a little more, the standard is 100 times times thinner, and then found the flaw in the mountains of "law" to find the corresponding one can be "tight"

How to classify the found defects in a strict hierarchy

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.