High priority and low Severity defects

Suppose in one banking application there is one module ATM Facility. in that ATM facility when ever we are dipositing/withdrawing money it is not showing any conformation message but actually at the back end it is happening properly with out any mistake means only missing of message . in this case as it is happenig properly so there is nothing wrong with the application but as end user is not getting any conformation message so he/she will be confuse for this.

So we can consider this issue as HIGH Priority but LOW Severity defects..


About kuldeep kumar

i am a software engineer and working in an MNC.

Posted on March 1, 2007, in Manual Testing, Priority and Severity of Defects in Real Time App.. Bookmark the permalink. 16 Comments.

  1. great, its very much clarify my doubts.

  2. Hi,
    this is very good example for High priority and low severity,also tell can u pls the ex. for low priority and high severity.

  3. Hi,

    The way what you understood about priority & severity is really great, Because severity & priority is depend on business and technical functionality. so, as per the user’s perception & business perception whatever you stated is correct.

    Best regards,

  4. I follow your blog for a long time and must tell you that your articles are always valuable to readers.

  5. Hi! I was surfing and found your blog post… nice! I love your blog. 🙂 Cheers! Sandra. R.

  6. Gaurav Bhardwaj

    Great example.its unique and very good example.Its cleared the doubt and interesting sting also.thanks

  7. Good example

  8. I got good a clarity from your live example. Its great from you. Thanks a lot.

  9. I have cleared my doubt with your example. Thanks Shiva

  10. good example to understand ..

  11. I don’t think ,in this case severity is low,because according to customer requirement it should display the confirmation message,but it not displayed..one thing is that severity display the affection on appication. If it not display the confirmation message,it not working his functionality….in this case we give the severity medium ,not low.

  12. Woah! I’m really digging the template/theme of this website. It’s simple, yet effective.
    A lot of times it’s very hard to get that “perfect balance” between usability and visual appearance. I must say you’ve
    done a superb job with this. Also, the blog loads very fast for me
    on Chrome. Superb Blog!

  13. Greetings! I’ve been following your web site for some time now and finally got the bravery to go ahead and give you a shout out from New Caney Texas! Just wanted to tell you keep up the great job!

  14. You really created a number of superb tips within ur article, “High
    priority and low Severity defects | KR Testing Solutions”.
    I may you should be coming back again to ur web site before long.
    Thank you -Janina

  15. “High priority and low Severity defects | KR Testing Solutions” was
    indeed a quite pleasant post, . Keep creating and I will continue viewing!
    Thanks ,Lincoln

  16. Prasad..

    Severity always thinks about user i.e way tester sets Severity.
    Priority is how soon that bug to be fixed.

    so in above ATM example I will say it is high Severity and medium Priority issue.
    because transaction is done successfully but ATM didn’t displayed confirmation message, the user is in confusion that his transaction is successful or not, so as a user point of view it is big issue Priority is medium as it is not a blocker.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: