Priority and Severity Examples

Can some one give the best example for the following scenario's
1. High Priority and high severity
2. High Priority and low severity
3. High severity and low priority
4. low severity and low priority

Questions by Meenal001

Editorial / Best Answer

be.priyanka  

  • Member Since Dec-2007 | Mar 3rd, 2008


Priority - Priority is the order in which developer has to fix the bug.
Severity - Severity is how seroisly the bug is impacting the application.

Eg.


High Priority & High Severity: A show stopper error which occurs on the basic funcationality of the application . (Eg. A site maintaing the student details, on saving record if it, doesn't allow to save the record then this is high priority and high severity bug.)

High Priority & Low Severity: The spell mistakes that happens on the cover page or headin or title of an application.

High Severity & Low Priority: The application generates a show stopper or system error, (for which there is no workaround) but on click of link which is rarely used by the end user.


Low Priority and Low Severity: Any cosmetic or spell issues which is with in a paragraph or in the report (Not on cover page, heading, title).

Plz correct me if i am wrong.

Showing Answers 1 - 7 of 7 Answers

Severity is the measure as to what extent the defect is harmful for the application, on the other hand Priority is releated, as to which defect the tester wants the dev team to fix first.

A defect say a spelling error in the application is a cosmetic defect, but if that occur on all the screens of the UI, then that makes it a high priority, so this is an example of High priority and low severity.

A system crash is an example oh high severity, but suppose that occurs when user click a button and the usage of that too is very low, so there is no urgency to fix it now, so this is an example of low priority and high severity. 

  Was this answer useful?  Yes

Priority - Priority is the order in which developer has to fix the bug.
Severity - Severity is how seroisly the bug is impacting the application.

Eg.


High Priority & High Severity: A show stopper error which occurs on the basic funcationality of the application . (Eg. A site maintaing the student details, on saving record if it, doesn't allow to save the record then this is high priority and high severity bug.)

High Priority & Low Severity: The spell mistakes that happens on the cover page or headin or title of an application.

High Severity & Low Priority: The application generates a show stopper or system error, (for which there is no workaround) but on click of link which is rarely used by the end user.


Low Priority and Low Severity: Any cosmetic or spell issues which is with in a paragraph or in the report (Not on cover page, heading, title).

Plz correct me if i am wrong.

Nitinkk

  • Aug 27th, 2009
 

Regarding Priority and Severity Examples :

What most of the testing Guys do while answering the Simple question they took the examples from the Global project. ( Like , I got this & that in YAHOO, REDIFF)

I my opinion this is Bad Habit , Always give the Example from ur current / previous projects. It actaully leaves a good impression on the Interviewer.

U have the Concept of what "Priority" and "Severity"  is ..

Prepare the Examples from ur current / previous projects.


Regds,
Nitin K Verma

  Was this answer useful?  Yes

High priority and high severity:  The application crashes whenever a person attempts to submit valid input on the registration page.

High priority and low severity:  The content entered in the Terms of Use are not correct and could potentially lead to legal consequences.

High severity and low priority:  The application crashes whenever a person enters 1500+ chars in a phone number text box that should accept no more than 15 chars.

Low severity and low priority:  There is a slight misspelling on one of the FAQ pages.


  Was this answer useful?  Yes

Kriya More

  • Jun 19th, 2014
 

1.Let us assume a scenario where a Login button is labeled as Logen
The priority and severity for different situations may be expressed as:-
1.For GUI testing: it is high priority and low severity
2.For UI testing: it is high priority and high severity
3.For functional testing: it is low priority and low severity
4.For cosmetic testing: it is low priority and high severity


Low Severity, Low Priority
Suppose an 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 wont affect any functionality or the credibility of the company.

Low Severity, High Priority
1.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.
2.Any typo mistakes or glaring spelling mistakes on home page.

  Was this answer useful?  Yes

anusha

  • Jun 23rd, 2014
 

how to test

  Was this answer useful?  Yes

swastika soni

  • Jul 15th, 2014
 

Priority means the importance of fixing the bug and severity means to decide the level of bug.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

Answer Question

Click here to Login / Register your free account


 
Send   Reset

 

Related Answered Questions

 

Related Open Questions