Scenerios for high severity low priority

Hi friends

can somebody give scenarios for low priority and high severity and high priority and low severity?

Hi Sanjeev,

Please find enlisted a few scenarios -
[COLOR="Blue"][U]High Priority but Low Severity[/U][/COLOR]
[LIST]
While Developing a site for Pepsi, by mistake a logo sign of coke is embedded. This does not affect functionality in any way but has high priority to be fixed.[/LIST]
[LIST]
Any typo mistakes or glaring spelling mistakes on home page which are discovered during UAT testing.[/LIST]

[COLOR="blue"][U]Low Priority but High Severity[/U][/COLOR]
[LIST]
Incase application works perfectly for 50000 sessions but beings to crash after higher number of sessions. This problem needs to be fixed but not immediately.[/LIST]
[LIST]
Any report generation not getting completed 100% - Means missing Title, Title Columns but having proper data enlisted. We could have this fixed in the next build but missing report columns is a High Severity defect.[/LIST]

Some might consider Numeric field level validations also as Low Priority but High Severity defects coz when valid data is entered functionality proceeds correctly. But incase of wrong value entry application could crash as well if no error trapping is not provided.

Cheers....

Hi sanjeev,

Inter-relate the examples given by Umesh with the definitions below you will find the things very easy to understand:

<b>Defect Severity: </b>
Severity is the seriousness of the defect or bug in terms of functionality. Severity is usually set by the QA team to intimate the Development team

The severity of defects is classified as follows:

<b>Critical</b> The problem prevents further processing and testing.

<b>High</b> The problem affects selected processing to a significant degree, making it inoperable, Cause data loss, or could cause a user to make an incorrect decision or entry.

<b>Medium</b> The problem affects selected processing, but has a work-around that allows continued processing and testing. No data loss is suffered. These may be cosmetic problems that hamper usability or divulge client-specific information.

<b>Low</b> The problem is cosmetic, and/or does not affect further processing and testing.

<b>Defect Priority:</b>
Priority tells us how soon it is desired to fix the problem. Priority is the importance of defect in terms of customer's requirements.

Priority is set by the Business / Development Lead for the Development team to prioritize in fixing the defects

<b>High</b> Must fix the problem NOW (All other defect fixing tasks take least preference). Problem is blocking further progress in this area.

<b>Medium</b> Should fix the problem soon, before product release

<b>Low</b> Fix the problem if time permits; somewhat trivial. May be postponed

<b>Note:</b> There are different ways of representing the Priority and Severity based on the project requirement.

very useful info!!!!!!!!!thanks

Since bizzzzzare has already mentioned the two cases, I will take a shot at the other two, for readers who want to learn more..

[B]3. Low Priority, Low Severity[/B]
Suppose your application (web) is made up of 20 pages. On one of the pages out of the 20 which is visited very infrequently, there is a sentence with a grammatical error. Now, even though it’s a mistake on this expensive website, users can understand its meaning without any difficulty. This bug may go unnoticed to the eyes of many and won't affect any functionality or the credibility of the company.

[B]4. High Priority, High Severity[/B]
Now assume a windows-based application, a word-processor let’s say. As you open any file to be viewed it in, it crashes. Now, you can only create new files but as you open them, the word-processor crashes. This completely eliminates the usability of that word-processor as you can’t come back and edit your work on it, and also affects one of the major functionalities of the application. Thus, it’s a severe bug and should be fixed immediately.

Hi sanjeev, the bug severity and priority is depends on the testing type which we are couducting.
Here i will give example of defferent types of testings.
Suppose ok button is labled as oke :
for gui testing : it is high priority and low severity
for ui testing: it is high priority and high severity
for functional testing: it is low priority and low severity
for cosmetic testing: it is low priority and high sevirity
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Arun Singh Rajaputra
Software Test Engineer

Defect having any critical functional related issues we can say High severity
where as defects having less impact over functionality can be treated as low seveiority.


But I also like to know various combinations of high severity with low priority & vice-versa