Differentiate between severity and priority? who assign
these parameters to a bug?
- 6 Answers
- 11183 Views
- Satyam, I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / rumana farheen
Severity:the seriousness of the defect in terms of the
functionality is known as Severity.
Critical:not able to continue testing without resolving the
defect
Ex:application crash, database corruption
Major:able to continue but mandatory to resolve
Minor:able to continue testing but may or may not resolve
Priority:the importance of the defect in terms of customer
is known as Priority.
depending on the severity of the defect the priority is
given.
Either high, medium or low.
| Is This Answer Correct ? | 8 Yes | 1 No |
Answer / nag
Severity:-Seriousness of the defect,Bcoz of this defect how
much impact on the application
Priority:-importance of the defect,Bocz of the defect
whether any business loss
based on priority level defect will be fixed
EX:-Assume one online bank application was developed all
functionalitys working correctly but Bang name was written
wrongly(intead of icici they written hdfc)
here bcoz of wrong name system not getting any effect but
whole business will get effect, customer will be confused
so here, severity is low priority is high
so it must fix as possible as early
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / nuve1284
Severity: how much the
bug/defect is going to impact the application.
Priority:Depending upon the servity the priority will be
assigned and its helps the developer like how soon a
particular defect has to be fixed.
The following are the types of Severity
Show stopper
Severe
Major
Minor
The following are the types of Priority
High
Medium
Low
Generally the tester assigns the severity and developer
assigns the priority and it depends on the client u are
wiorkig and their practise in QC.
For more info about manual and automation testing
www.swaretesting.blogspot.com
www.qtestpro.blogspot.com
| Is This Answer Correct ? | 4 Yes | 1 No |
Severity:rates the bug as either it belongs to major,minor
or trivial.
Priority:rates comes under high,medium low.
ex: part severity priority
a major medium
b minor high
c trivial low
always we have to work on bugs based on priority wise only.
because of priority only we can clear other major issues
since one of minor issues may affect the working of other
major parts.and also the client may analyse the issue and
change the requirement.some times even the severity is low
if the priority is high we have to work on that coz it
might be waiting for delivery.
here we need to concentrate on part b in the given ex.
| Is This Answer Correct ? | 3 Yes | 1 No |
Answer / s33.aditya
Severity:It is the criticality of the bug. i.e how much the
bug is going to impact the application.
Priority:Depending upon the servity the priority will be
assigned.
The following are the types of Severity
Show stopper
Sever
Major
Minor
The following are the types of Priority
High
Medium
Low
The one who finds the bug will assign these, some time the
senior person(Lead) will assign
| Is This Answer Correct ? | 2 Yes | 0 No |
Answer / rumana farheen
Priority:the importance of defect fixing in terms of
customer is known as Priority.
High: for critical defects
Moderate: for major defects
Low: for minor defects
Thank you
| Is This Answer Correct ? | 1 Yes | 1 No |
WHAT IS SDLC? WHAT IS STLC? WHAT IS THE DIFFERENCE BETWEEN SDLC AND STLC?
Tell the procedure to close word file?
what is system testing?
Could anyone explain me how to write scenerio for login screen?
What is bidirectional traceability?
Guys, can any one of u give the realtime example for Unit Testing?
1Who performed sanity and smoke testing :-- developers or testers ? Explain with example and prove ur answer. 2 Company has developed a project for company B, company B has to introduce this project into the market. The acceptance testing is performed at Company B. is it called as alpha testing or beta testing ? Explain with example and prove ur answer.
What is the example of Integration Testing?
Describe components of a typical test plan, such as tools for interactive products and for database products, as well as cause-and-effect graphs and data-flow diagrams.
Configuration Management is 1)before System Requirement 2)at Start of the S.D.L.C 3)at Start of the S.T.L.C 4)at the time of Coding. Would be better if anyone can provide some explanation for the answer
differentiate defect age build interval? what style of testing we can follow with lack of documentation?
what is low seviority high priority defet (ex: Yahoo mail)
Automation Testing 
