Page 1 of 3 123 LastLast
Results 1 to 20 of 45

Thread: Which is given first preference priority or seviority

  1. #1
    Junior Member
    Join Date
    Jun 2006
    Answers
    10

    difference between severity and priority

    Plz explain with example about 1. hight severity and hight priority
    2. low severity and low priority
    3. low severity and high priority
    4. high severity and low priority


  2. #2
    Expert Member
    Join Date
    Sep 2005
    Answers
    206

    Re: difference between severity and priority

    Priority determines the urgency or order of importance of the bug.

    Severity determines the state or quality of being severe,how severly it affects the system.

    Severity is a technical issue where as priority is a business issue.

    This is also Based on the Business Rule. Team leader or QA person gives priority.


  3. #3
    Junior Member
    Join Date
    Jun 2006
    Answers
    1

    Re: difference between severity and priority

    Hi, Sunny

    I will give you an example like "If a system is going to crash and an alert comes saying do u want that action to be perfformed or not?" If no is clicked and even then system crashes it severe one but priority is low bcos if we change action of no button to yes ...it will be fine working..


  4. #4
    Contributing Member
    Join Date
    May 2006
    Answers
    71

    Re: difference between severity and priority

    Hi,
    It is very essential to know about severity and priority since this only determines about how fast and how important the bug or error is and needs attention. It is based on this the developer or tester prioritize their work schedule. Severity tells us how bad the defect is. Priority tells us how soon it is desired to fix the problem.

    Regards,
    Fred


  5. #5
    Expert Member
    Join Date
    May 2006
    Answers
    114

    Re: difference between severity and priority

    To add more to this let me tell about the values severity can take like Major, Minor or
    Trivial and similarly priority can take values like 1, 2 or 3 etc where 1 is usually used to denote error with high priority defect.


  6. #6
    Contributing Member
    Join Date
    May 2006
    Answers
    85

    Re: difference between severity and priority

    The above values are needed because if the severity is major then it denotes more attention like instances of system crash or error message forcing to close the window so on. If the severity is minor then it represents low attention like instances of error only in certain parts of the application or error only during certain times.


  7. #7
    Junior Member
    Join Date
    Nov 2006
    Answers
    12

    Re: difference between severity and priority

    seviority describes how serious the defect is. classified into 4 types
    fatal, major,minor,suggestions

    priority describes the sequence in which the defects have to be described
    classified into 4 types

    critical,high,medium,low

    eg:there was an bus accident few members injured
    seviority / priority
    one went into coma fatal / critical
    one lost more blood major / high
    one unable to walk minor / meduim
    one is talking had small injuries minor / low
    one is ok suggestions / low
    if any doubts ask
    madhav_sus@yahoo.co.in

    Last edited by msusmitha; 12-01-2006 at 06:18 AM. Reason: understandability

  8. #8
    Expert Member
    Join Date
    Nov 2006
    Answers
    518

    Re: difference between severity and priority

    If a detected bug effects the system or s/w under testing and is crucial, then its severity would be high. But if it effects our business process, then its priority is high. In some cases, a low priority bug may be given a high priority sequence if it is believed that it takes long time to resolve the issue and the time in hand would not be sufficient.

    Eg.
    1. high severity and high priority - Database connectivity cannot be established by multiple users.

    2. low severity and low priority - Small issues like, incorrect number of decimal digits in the output.

    3. low severity and high priority - Images not updated.

    4. high severity and low priority - In a module of say 2 interfaces, the link between them is broken or is not functioning.


  9. #9
    Expert Member
    Join Date
    Apr 2006
    Answers
    124

    Re: difference between severity and priority

    Here are some of the examples ...

    High severity
    high prority : database not getting connected., internal server error for webpages
    low priority : price field taking $,. And numeric data... But also saving other special characters like @# etc.,
    medium severity
    high priority : help messages missing..
    Low priority : help message is displayed but too complex to understand
    low severity
    high priority : spelling mistakes, logo or image not updated
    low priority : improper allignment, grouping of objects

    anyone of u find anything wrong pls do indicate...


  10. #10
    Contributing Member
    Join Date
    May 2006
    Answers
    78

    Examples of severity and prority bugs

    Can anybody tell me examples of
    1. High severity and High Proirity bugs
    2. High severity and low proirity bugs
    3. Medium severity and High Proirity
    4. Medium severity and Low Proirity
    5. Low severity and High Proirity
    6. Low severity and LowProirity
    and in what basis we will give prority?


  11. #11
    Expert Member
    Join Date
    Apr 2006
    Answers
    124

    Re: Examples of severity and prority bugs

    Bharathi refer to "difference between severity and priority" posted in Software Testing

    http://www.geekinterview.com/talk/18...-priority.html


  12. #12
    Expert Member
    Join Date
    Nov 2006
    Answers
    518

    Re: Examples of severity and prority bugs

    Eg.
    1. high severity and high priority - Database connectivity cannot be established by multiple users.

    2. low severity and low priority - Small issues like, incorrect number of decimal digits in the output.

    3. low severity and high priority - Images not updated.

    4. high severity and low priority - In a module of say 2 interfaces, the link between them is broken or is not functioning.

    Lack of WILL POWER has caused more failure than
    lack of INTELLIGENCE or ABILITY.

    -sutnarcha-

  13. #13

    Re: Examples of severity and prority bugs

    Quote Originally Posted by bharathi_ark View Post
    Can anybody tell me examples of
    1. High severity and High Proirity bugs
    2. High severity and low proirity bugs
    3. Medium severity and High Proirity
    4. Medium severity and Low Proirity
    5. Low severity and High Proirity
    6. Low severity and LowProirity
    and in what basis we will give prority?
    Hii Friend.........
    My personal view about this is. If u r saying High Priority or Sevirity u must hav the reason to satisfy othrs tht why u saying so or why u assigned.U must have proper reason to say tht, so tht u can prove why it is so.

    Now wht I think abt these terms
    Priority:-
    How quickly u need to fix tht bug.
    Severity:-
    How critically it wil affect the system as a whole
    E.g. :-
    1.High P & Low S.
    name speling of organisation on site.
    Reason-> It's High priority coz ur client pay u tht much cost & u given tht mistake even the name of org is wrong on site.Although it will not affect the organisation system in any way.So u can c it as high priority.

    Note-> Friends Still the application under Testing when we discovered that defect.

    2. High S & Low P:
    (i) Any module added in the system goes to affect the whole working of
    the system.
    (ii) System delivered neds to done some critical changes tht only done by
    org. person , simple person can't do it cause it wil shut off the whole
    system.

    (Reason behind High sevirity systems mainly or 99% is that it wil daimage
    or affect the systems particular module or component but still can be recoered from that but
    rigriously.so I given that as High Severity.)

    3. Low P & Low S:
    Logo of Org. Shown in left top corner but as client requirments or
    discussions he/she want it in Right Top Corner.

    (Reason-->Any Bug discovered in the system at later stage tht dosn't
    hav as such affect on system can sy just like tht if not corrected thn
    no effect on systm it's working properly. But as requirment it should not
    b thr in the system.)

    4. High Severity & High Priority
    Suppose any Button on the interface through which personal/ secerate
    record of org. get accessed & tht button is available only for the top MGT
    ppls. But aas defect in the system it's also made available to all ppls.

    So just think about it it's have high severity coz org. secerates can be theft frm thr & tht wil definity affect the org. as a whole if they loose thr secerates to thir enimies. High priority bcoz it's dangerious if in hands of all so need to fix as soon as or can say as early as possible.


    So dear friends I think Now u got the concept of these minute differences.

    Plz correct me If I m wrong, I wil b thank full to u.
    .......Wishing U happy new Year.......

    Thnx & regards
    Rajeev Sharma
    91-9818004180


    Last edited by Rajeev Kant Sharma; 02-03-2007 at 06:46 AM.

  14. #14
    Junior Member
    Join Date
    Feb 2007
    Answers
    4

    Priority, severioty

    Hi All,

    I am working as testing engineer, still im in confustion what is severioty and what is priority. Who gives the severioty and who gives the priority.
    I think tester gives the severiry and developers gives the priority..is it right?


  15. #15
    Expert Member
    Join Date
    Jan 2007
    Answers
    249

    Re: Priority, severioty

    Hi,

    Severity defines impact of the defect. Priority defines the urgency of the defect to get fixed.

    In my company the method we follow is,

    Severity is given by Testers and Priority is given by PM's(Project Managers).
    I think developers wont give priority... because the chance of giving high priority is less in that case...

    Thanks
    Manoj


  16. #16
    Contributing Member
    Join Date
    Jan 2007
    Answers
    31

    Re: Priority, severioty

    hi,

    i will try to put in simple words:

    Severity: Its the impact or importance of bug with respect to application. (i.e. how much that bug will be hampering the application process.)

    Priority: its the importance of the bug with respect to all the bugs. (u can say it gives an idea which bug has to be fixed first.

    regards,
    RSY


  17. #17
    Expert Member
    Join Date
    Sep 2006
    Answers
    477

    Re: Priority, severioty

    Sorry guys, there is already a thread for this.
    http://www.geekinterview.com/talk/182-difference-between-severity-and-priority.html?highlight=priority


    I can merge these posts into that thread. In fact that is the only thing I can do. While starting a thread please check if the question/topic is already posted or not by running simple search in the forum.

    Thanks. Hope to see some great post from you guys.

    Cheers!
    Kalayama

    [COLOR="Blue"][SIZE="2"]"If you are not living on the edge of your life, you are wasting space"[/SIZE][/COLOR]

    Someone says "Impossible is nothing". The man next him says "Let me see you licking your elbow tip!"

  18. #18
    Junior Member
    Join Date
    Feb 2007
    Answers
    5

    Re: Priority, severioty

    Severity is how severe the bug is and Priority is the importance of the bug with respect to other bugs to be fixed.
    Severity of the bugs is given by Testers
    Priority of the bugs is decided by Project Managers.


  19. #19
    Junior Member
    Join Date
    Jun 2006
    Answers
    17

    Re: difference between severity and priority

    HI,

    Severity is nothing but the impact of a bug interms of application.
    priority is nothing but the impact of a bug interms of client requirements.

    GEnerally severity is set by testers and priority is set by Tl or PL.


  20. #20
    Junior Member
    Join Date
    Dec 2006
    Answers
    20

    Re: difference between severity and priority

    A brief explanation of priority and severity. Priority is how a bug affects the customer. For example, if the main feature of the application isn't working, it has a high priority. If a rarely used feature of the application isn't working, this is a low priority. Severity is how bad the bug itself is. If there is an obvious workaround for the user, this is a low severity. If the application throws an exception and shuts down, this is a high severity. It is possible to have a high priority, low severity bug or a low priority, high severity bug. To make matters more interesting, some companies have a third field, impact, that is a function of priority and severity. Impact is used to make final decisions about which bugs will get fixed, and which will not. We will not use that here.

    Example
    Here's a sample for a bug in a calculator:

    Title: Multiplying 3 numbers does not work

    Reproduction steps:

    Start application
    Click a number
    Click *
    Click another number
    Click *
    Click a third number
    Click =

    Expected output: The multiplication of all three numbers

    Actual output: The multiplication of the last two numbers only

    Priority: 1

    Severity: 2

    The priority was 1 since this is a main feature of a calculator. The severity is 2 because users do have a workaround of multiplying separately, annoying as it is. A less annoying workaround would cause the severity to go down.

    Turn in your list of manual bug reports in manual.html. Notice that bugs listed here must also be in bugs.html.

    HINT: Some bugs are obvious errors in the feature. Others are subtle in that the user interface is misleading for the user. All of these are bugs!

    HINT: Remember that different users will accomplish the same task in a different way. Don't go about your normal application usage. Test all possibilities!


  21.  Sponsored Ads
    Ad


     
Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
About us
Applying for a job can be a stressful and frustrating experience, especially for someone who has never done it before. Considering that you are competing for the position with a at least a dozen other applicants, it is imperative that you thoroughly prepare for the job interview, in order to stand a good chance of getting hired. That's where GeekInterview can help.
Interact