Defect Thrashing Procedure

By the term “Defect Thrashing”, we mean assigning a priority to a defect. A team of individuals does "Defect Thrashing". Representatives from R &D, PM and QA prioritize defects on a regular basis depending on the development phase. Product Management always has the authority for overriding the priority.

The setting of priority of the defect is an automatic process. The QA Engineer responsible for the defect thrashing has to answer the following questions.

• What is the impact on customer workflow?
• Does this Bug stop us from Testing?
• What is the probability of occurrence or occurring in workflow of customer?
• What is the origin of the defect?
• What is the impact of the defect on other related modules?


Depending upon the answers provided to the above questions by the QA Engineer, the system automatically assigns a priority to the defect.

For more software testing definitions, please go here