Bug classification - setting priority, severity

Bug classification is one of the trickiest part in testing. Day in day out, I see bugs being reprioritized and severity being raised or lowered.

As testers it is very important for us to understand how to classify a bug with a proper severity and priority.

Broadly I would define them as follows:

  1. Severity - how much damage a bug is doing to the application under test. Open bugs which have high severity are potential release stoppers. If released with these bugs, there is a possibility of customer dissatisfaction or loss of revenue which is definitely not desired.
  2. Priority - how important it is to fix that bug for this release. A bug with a high priority is again a potential release stopper. If a bug fix can be postponed for a later release and does not impact customer experience or cause loss of revenue, it can be of lower priority.

 


User login

Who's new

  • amitbhagwat
  • TenLekerand
  • ClainaNaigh
  • RaviGunasekaran
  • gopasruhafoni

Who's online

There are currently 0 users and 0 guests online.