Hence when it comes to bugs, the severity of a bug would indicate the effect it has on the system in terms of its impact. Severity by the English definition is used to describe the gravity of an undesirable occurrence.
Therefore in the context of defects, the priority of a defect would indicate the urgency with which it would need to be fixed. Priority by the English definition is used in the comparison of two things or conditions, where one has to be given more importance than the other(s) and has to be tackled with/resolved first before proceeding to the next one(s). Let’s understand briefly the theoretical definitions of the two parameters in the next section. There’s a fine line between the two and it’s important to understand that there are indeed differences between the two. These are often a confusing concept and are almost used interchangeably amongst not only test teams but also development teams. The two main parameters that form the basis for effective Defect Tracking and Resolution are:
This, in turn, would help in efficient defect tracking/maintenance processes and would also form the basis for quicker defect turnaround time. In line with defect maintenance processes, when any tester files a defect- apart from the method/description to reproduce the issue seen, he has to also furnish some categorical information that would aid inaccurate classification of the defect. In such a scenario, managing these defects and analyzing these defects to drive closure can be a daunting task.
ISSUE PRIORITY MATRIX SOFTWARE
This is important because test teams open several defects when testing a piece of software which is only multiplied if the particular system under test is complex. One of the important aspects of the Defect Life cycle on a generic level includes defect tracking.
0 kommentar(er)
