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..
Posted on March 1, 2007, in Manual Testing, Priority and Severity of Defects in Real Time App.. Bookmark the permalink. 9 Comments.
great, its very much clarify my doubts.
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.
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,
lohith
9902054966
I follow your blog for a long time and must tell you that your articles are always valuable to readers.
Hi! I was surfing and found your blog post… nice! I love your blog.
Cheers! Sandra. R.
Great example.its unique and very good example.Its cleared the doubt and interesting sting also.thanks
Good example
I got good a clarity from your live example. Its great from you. Thanks a lot.
I have cleared my doubt with your example. Thanks Shiva