Resolved Question
Priority and Severity Examples
 
Details: 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
  asked by: chickalltheway  on: Jun 21, 2009  
 Best Answer ! ! !
carecare 's Answer  ( this answer is maked as best answer of this question at: Jun 28, 2009 )


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.

1 comments  answered on: Jun 23, 2009 
Other Answer (3)
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.
  game88   answered onú║Jun 22, 2009  1 comments

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.

  kel13   answered onú║Jun 24, 2009  0 comments

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

  wuii   answered onú║Jun 25, 2009  0 comments

Hot Questions

Contact Us - IT-Interview