Priority and Severity

Q. What is a test strategy?

Answer:
A test strategy must address the risks and present a process that can reduce those
risks.
The two components of Test strategy are:
a) Test Factor: The risk of issue that needs to be addressed as a part of the test
strategy. Factors that are to be addressed in testing a specific application
system will form the test factor.
b) Test phase: The phase of the systems development life cycle in which testing
will occur.]

Q. When to stop testing?

Answer:
a) When all the requirements are adequately executed successfully through test
cases
b) Bug reporting rate reaches a particular limit
c) The test environment no more exists for conducting testing
d) The scheduled time for testing is over
e) The budget allocation for testing is over]

Q. Your company is about to roll out an E-Commerce application. It is not
possible to test the application on all types of browsers on all platforms and
operating systems. What steps would you take in the testing environment to
reduce the business risks and commercial risks?

Answer:
Compatibility testing should be done on all browsers (IE, Netscape, Mozilla etc.)
across all the operating systems (win 98/2K/NT/XP/ME/Unix etc.)]

Q. What’s the difference between priority and severity?

Answer:
“Priority” is associated with scheduling, and “severity” is associated with standards.
“Priority” means something is afforded or deserves prior attention; a precedence
established by order of importance (or urgency). “Severity” is the state or quality of
being severe; severe implies adherence to rigorous standards or high principles and
often suggests harshness; severe is marked by or requires strict adherence to
rigorous standards or high principles, e.g. a severe code of behavior. The words
priority and severity do come up in bug tracking. A variety of commercial, problemtracking/
management software tools are available. These tools, with the detailed
input of software test engineers, give the team complete information so developers
can understand the bug, get an idea of its ‘severity’, reproduce it and fix it. The fixes
are based on project ‘priorities’ and ‘severity’ of bugs. The ‘severity’ of a problem is
defined in accordance to the customer’s risk assessment and recorded in their
selected tracking tool. A buggy software can ‘severely’ affect schedules, which, in
turn can lead to a reassessment and renegotiation of ‘priorities’.]

------------




The Best Software Testing Training You'll Ever Get!

software testing course QA training

89 comments ↓

#1 Viky

How priority and severity are determined?
Are they only decided by the tester by his own or is there any fix criteria to decide it?
I mean if i found a bug i will assign it priority what i think is relative but for the same bug other tester can assign different priority and severity … so how should one maintain this as a standard?

#2 Ashwini

Q. When to stop testing?

Answer:
a) When all the requirements are adequately executed successfully through test
cases
b) Bug reporting rate reaches a particular limit
c) The test environment no more exists for conducting testing
d) The scheduled time for testing is over
e) The budget allocation for testing is over

if we have multiple option question
then which of the above is most correct answer

#3 Avdhesh

I feel, none of above mentioned options are adequate to stop testing.
I could have been,
1. Raised defect status are of low priority having very less impace on system
2. Business agrees to stop the testing & is ready to bear all the risk
3. Atleast all the high priority requirement related test cases are covered.

#4 pawanbudur

give more examples for priority and severity defects

#5 Subha Viswanathan

IN general the tester only assigns severity to the bug. The priority is assigned by the project manager. The priority of the bug might differ according to the release and hence the project manager will assign priority depending on how important that bug fix is for the release.

Please correct me if i am wrong.

-subha

#6 Prabhu

Would like to know what is the difference between test plan and test stratergy.

#7 john

severity means how serious the bug is?
pripority means a message to the developer what defect are taken first ,next and ;last for defect recttification

#8 Beena

How to decide the priority and severity ?

#9 sarika

your answer provide nice information ,but i have one
quiery that is
“can priority dependes on severity”?

please answer my quiery.

#10 isha

who decides the priority devloper or QA?

#11 khema

QA
Base on client requirements we decided the priority.
Means the importance of the client requirement we give the priority…

#12 sharmi

Can anyone give examples for all combinations of priority and severity like high priority and low severity,etc…

#13 Meghmala

Hi all,

Can anyone tell me procedure for testing performance of web apps ?
I am single tester in my company. I want to do load /stress testing.
Please help me.

#14 yogshesh

u all hvnt gve the live examples of severity and prioroty .so plkease try to gve the examples

#15 venkat

Hi Meghmala,

can you please tell me which automation tool using for performance testing?

The process is depending on the tool!!!

Please get back on nvenkii@gmail.com

#16 Ashwini

To decide the severity of the bug, tester has to follow the Bug categorization document designed by the Test architect in the company.
Different product or application have different severity based on the customer requirements.

#17 Dhruv

Priority and Severity are subjective term both completely depends upon domain in which you are and phase in which your project is e.g If you are in banking domain then bug in spealing, logs will have less severity but if you in E-learning domain then spealing and logs, pictures will have high severity.So deciding severity and Priority is tester job but after haveing word with the Team lead or the Manager.

#18 Ashwini

While creating the bug, severity has to be decided by the test engineer based on the Bug categorization document, and Priority has be decided by Software Developer or Project manager who is leading the project for which Testing is done by Software Quality Assurance(SQA) team.

Any questions, please write to me at aashwini.r@gmail.com

#19 Ashwini

Correction in email id: please write to me at ashwinir@gmail.com

#20 satish kumar kurra

Severity: It is the seriousness of defect in terms of Functionality
Priority: The importance of defect to resolve w.r.t Customer/Client/User

#21 Nikki

Here are some definitions to keep in mind when submitting a bug in Bugzilla:

SEVERITY
Define defect severity value by Bugzilla default severity definition. The severity describes the impact of a bug.

Blocker: Prevents developers or testers from performing their jobs. Impacts the development process.
Critical: Crash, loss of data, corruption of data, severe memory leak.
Major: Major loss of function, as specified in the product requirements for this release, or existing in the current
Normal: Non-major loss of function.
Minor: Issue that can be viewed as trivial (e.g. cosmetic, UI, easily documented).
Enhancement: Request for software enhancement, or any non-defect task or work item.
PRIORITY
Define defect priority value by Bugzilla default priority definition. The priority specifies the level of urgency to be resolved for the defect.

P1-Urgent: defects are urgent issues.
P2-High: defects must be resolved in this release.
P3-Medium: defects would like to be fix, but won’t hold shipment for them.
p4-Low: defects are not as strong as desirable.
Bugzilla has many fields that provide additional information (e.g., environment details, found in version, etc.). Please provide as much information as possible when logging bugs.

#22 Nikki

dig it?

#23 Navneet Gupta

Hello Dear,
Can i get a job in QA where as i’m doing software testing course.

#24 Leena K

Is there any checklist available to decide the severity and priority of a bug?

#25 smr

Companies performing software development must look at error severity from a user’s point of view. What follows is a very useful system for classifying errors. Use it in your computerized M.R. system. An M.R., or modification request, is entered into a computer by any individual discovering an error in any software. The severity of the error is expressed as a number between one and four, and is defined as follows:

1 – An error which causes a program or system interrupt, or which causes program execution to abort. System personnel refer to this type of error as a “show stopper”. This error has the highest severity rating.
2 – A severe error which causes a program not to perform properly or to produce unreliable results. Normally, the user cannot find an appropriate “workaround” for this type of error.
3 – An error for which, while not minor, a “workaround” solution can be found for the user.
4 – A minor error, a cosmetic change, or an enhancement.

It should be the policy that, once a severity “1” error is discovered, programmers and developers must work around-the-clock until the error is corrected. Software can never be released to customers with any severity “1” or “2” errors. Occasionally, a software release with some severity “3” errors will be permitted. However, these errors are documented along with the actions to be taken by users when encountering them. Normally, severity “4” errors would not delay a software release.

#26 Sonia

hello, can anyone please guide me about to write test cases and wanna to know about Bugzilla

#27 virendra patil

hi frinds,
can any one give me the difference between
retesting and regression testing?

#28 Gayathri L

Retesting is testing the new code again with the same set of test cases. But Regression testing is testing the existing functionality to verify that the new code has not unearthed any new defects in the existing functionality. Simply, regression testing is to verify that that existing functionality works as expected.

#29 Abhijit

Suppose u have the website “Google” and the home page is having two fields “Username” and “Password”.
Case 1: If the user try to login after entering the credentials and is not able to do so – High Priority High Severity.
Case 2: If the letter ‘o’ is missing from the website logo ‘Google’ hampering the organisation’s reputation but not affecting any of the functionality – High Priority Low Severity
Case 3: If the help option from the browser is displaying blank on clicking it – Low Priority High Severity (From functional point of view this error is sever but from a practical standpoint, not every one opening the browser will go for the help option)
Case 4: On logging into any website if the home page is not displaying a comma (‘,’) between two words which it should have displayed
(cosmetic issue) – Low Priority Low Severity.

#30 Tejaswini

Who decides the severity and priority for a bug?

#31 venkat.v@itimes.com

severity — tester

priority– business; after the daily defect call, based on the testing schedule.

#32 Guruprasad

The examples shared by Abhijit(#29 ) are very good. Now i have some what clear picture of Severity and Priority. Thanks Abhijit

#33 Vikash

things explain by Abhijith # 29 is good,

#34 Anjani Dubey

SEVERITY :Impact of a bug in applications.

Blocker, Critical, Major, Normal, Minor
PRIORITY: Effect of a bug in the applications

P1-Urgent: defects are urgent issues.
P2-High: defects must be resolved in this release.
P3-Medium: defects would like to be fix, but won’t hold shipment for them.
p4-Low: defects are not as strong as desirable.

So priority and serverty, define by the tester and priority fixed by only current issue and depend upon that issue serverity fixed.

#35 Prasad

Partially i agree with Anjani.

When tester testing the application, if he detected a defect which affecting the functionality, he knows how badly it affecting the funct to go ahead.
so while logging he will assign the serverity.

But i dnt think, tester will assign priority aswell, why because.. once the defect is logged, Project manager/BOD(PM, PL)will review and decide, how fastly it should be fixed.
as u said, urgent, high, medium, low.

#36 Neha

Really you explained very well.

#37 Neha

Sorry i haven’t mention the name. Its for Abhijit

#38 Deepthi

Can u pls let me make understand of priority and severity by giving more examples?

#39 swetha

Priority :- How quickly we need to fix the bug? Or How soon the bug should get fixed?

Severity : – How much the bug is effecting the functionality of the application?
Eg:-
High Priority —Low severity
High Priority — High Severity
Low priority —High Severity
Low priority — low severity
(1) High Priority and Low Severity
If a company logo is not properly displayed on their website.
(2) High Priority and High Severity
Suppose you are doing online shopping and filled payment informations, but after submitting the form, you get a message like “Order has been cancelled.”
(3) Low Priority and High Severity
If we have a typical scenario in which the application get crashed, but that scenario exists rarely.
(4) Low Priority and Low Severity
There is a mistake like “You have registered success” instead of successfully, success is written

#40 shatrunjay

severity tells us about the impact of defect on the application or software where

priority tell about its appearance to solve or it tell us when we have to solve that defect

#41 Mayasen

Nice explanation swetha. Wishes…!!

#42 simmi jaiswal

Anjani Dubey, sir u hv written very good example of severity and priority
sir plz tell me about the test cases and its major feature

#43 Suresh Bhandari

thanks Swetha for the examples

#44 pervendra

Good explanation swetha & abhijit.

#45 Vijesh

Can someone help me to get more information about the different automated tool and the study material for the same. Especially for Flex application, i have heard about Flex monkey one of the automated tool for flex application testing , but it was not working when i tried earlier.
You can get me in vijesh.vkv@gmail.com.
i might not be in touch with this website frequently.

#46 jithu

@swetha!!!
thanks 4 d brief explanations!!!!

#47 uma maheswari

very helpful material.thank you very much

#48 santhosh

Hi ,
Any one tel while putting issue , For functional error wat should have to mention weather Functional or Functionality . My senior said put Functionality .My boss saying use Functional. Pls tel what to use. And differnce for both.
Please get me in my mail as soon as possible: santhosh_dasarath@yahoo.ca

-Santhosh

#49 ramesh

priority: The Importence of the defect in terms of customer point of view/customer side people is called.

severioty: The seriousness of the defect in terms of functionality is called.

#50 sachin

very good material

#51 Sarla

HI All

Please give me another example of Low Priority and High Severity.

#52 Sarla

Thanks Swetha 4 d brief explanations!!!!

#53 Vasanth

thanks swetha. very good explanation with example, that clears my all doubts on these.

#54 vijay gupta

Priority :- How quickly we need to fix the bug? Or How soon the bug should get fixed?

Severity : – Means the impact of bugs on the application Eg:-
High Priority —Low severity
High Priority — High Severity
Low priority —High Severity
Low priority — low severity
(1) High Priority and Low Severity
If a company logo is not properly displayed on their website.
(2) High Priority and High Severity
Suppose you are doing online shopping and filled payment informations, but after submitting the form, you get a message like “Order has been cancelled.”
(3) Low Priority and High Severity
If we have a typical scenario in which the application get crashed, but that scenario exists rarely.
(4) Low Priority and Low Severity
There is a mistake like “You have registered success” instead of successfully, success is written

#55 vijay gupta

Define the Severity and Priority
Severity: Severity determines the defect’s effect on the application. Severity is given by Testers
Priority: Determines the defect urgency of repair.Priority is given by Test lead or project manager

1. High Severity & Low Priority : For example an application which generates some banking related reports weekly, monthly, quarterly & yearly by doing some calculations. If there is a fault while calculating yearly report. This is a high severity fault but low priority because this fault can be fixed in the next release as a change request.

2. High Severity & High Priority : In the above example if there is a fault while calculating weekly report. This is a high severity and high priority fault because this fault will block the functionality of the application immediately within a week. It should be fixed urgently.

3. Low Severity & High Priority : If there is a spelling mistake or content issue on the homepage of a website which has daily hits of lakhs. In this case, though this fault is not affecting the website or other functionalities but considering the status and popularity of the website in the competitive market it is a high priority fault.

4. Low Severity & Low Priority : If there is a spelling mistake on the pages which has very less hits throughout the month on any website. This fault can be considered as low severity and low priority.

Priority is used to organize the work. The field only takes meaning when owner of the bug
P1 Fix in next build
P2 Fix as soon as possible
P3 Fix before next release
P4 Fix it time allow
P5 Unlikely to be fixed
Default priority for new defects is set at P3

#56 Yaseen

Severity: If the bug is breaking the normal flow in the application or business level of the application

Priority: Out of “n” bugs reported by tester, further they should suggest the developers which bugs should be fixed first based on the requirements.Hence the developers will fix the bugs according to their priorities assigned.

#57 Suresh

Thank you Vijay gupta and Swetha for the good explanation with nice examples.

#58 Shilpa Churi

High Priority & High Severity:
1) 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.)

2) The application crashes whenever a person attempts to submit valid input on the registration page.

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

High Severity & Low Priority:
1) 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.

2) An application creashes after multiple use of the functionality (For Ex. “Save” button use 200 times then that application will crash.)

3) The application crashes whenever a person enters 1500+ chars in a phone number text box that should accept no more than 15 chars.

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

#59 Ayona

Priority – related to Business, business will set the priority

Severity – related to functionality , tester will set the severity

#60 Jency Sebastian

Thanks to u all….

#61 eswaran k

“Priority” is associated with scheduling, and “severity” is associated with standards.
“Priority” means something is afforded or deserves prior attention; a precedence
established by order of importance (or urgency). “Severity” is the state or quality of
being severe; severe implies adherence to rigorous standards or high principles and
often suggests harshness; severe is marked by or requires strict adherence to
rigorous standards or high principles, e.g. a severe code of behavior. The words
priority and severity do come up in bug tracking. A variety of commercial, problemtracking/
management software tools are available. These tools, with the detailed
input of software test engineers, give the team complete information so developers
can understand the bug, get an idea of its ‘severity’, reproduce it and fix it. The fixes
are based on project ‘priorities’ and ‘severity’ of bugs. The ‘severity’ of a problem is
defined in accordance to the customer’s risk assessment and recorded in their
selected tracking tool. A buggy software can ‘severely’ affect schedules, which, in
turn can lead to a reassessment and renegotiation of ‘priorities’.]

#62 satish

What is a bug? What is an issue? What is a defect. Are they similar or differ

#63 shoaib

hey its very good site can any ony one tell me something related to tracability matrix

#64 pavani

thanks to u all………..n if anybody know explain what are the metrics for testing…….it is the question asked by one of the mnc………..

#65 Preethi

The concept of Traceability Matrix is very important from the Testing perspective. It is document which maps requirements with test cases. By preparing Traceability matrix, we can ensure that we have covered all the required functionalities of the application in our test cases

#66 sirisha

Hi Everybody,
Can anyone answer the following questions.
1.Write the test scenarios and test cases for online banking account,Checking account and Savings account.
2.Explain about the configuration management
3.Seviority and Priority levels related banking domain with examples
4.Exaplain the testing process in QTP
5.Explain the Data drivven framework

#67 sirisha

Please anwer above mentioned my questions and send a mail to : sirisha.kallu@gmail.com and thnks to everyone

#68 shanmuka vijay

severity means how it is impacting to the application and priority means how soon the developer must fix it so he can go forward for testing

#69 rajesh

Priority indicates how soon the bug should be fixed.
Severity indicates how severe the bug is.

#70 Saurav

What is the basic difference between Integration and regression testing. Between these two which should be done first and why?

#71 VARUN

Nice Explanation by Nikki… Thankssssssssss

#72 VARUN

To the Point Explanation by Shilpa Churi .Good.
Can AnyOne Give Severity and priority in terms of banking Domain.?

sharma21varun@gmail.com

#73 Jayaprashant

How do you define the Severity and Priority?
1)Severity of a Bug is defined as how impact the bug in the Scenario or the effectiveness of the bug as per the functionality and Requirement.It is always reported by a tester.
2)Priority is defined by devloper to prioritise the order in which the bug has to be fixed.

#74 Gaurav

Severity: is Seriousness of the problem(Defect) in terms of Functionality.
Ex- System crashed when u hit a button, but the page where the button is located is the part of next release.

Priority: is urgency of fixing the problem(Defect) in terms of user/client/customer point of view
Ex: Spelling Mistake in Company Website.

If u have any other query then U can reach me @gauravjaincool@gmail.com

#75 wish

severity is decided by a tester and priority is decided by dev manager in QA testing.

#76 Carlos

Well Done……..Very nice information………Hope it helps in cracking SEV & PROI question in interview:) Many thanks.

#77 Rajesh.K

Hi all

#78 KNR

Well Done……..Very nice information………Hope it helps in cracking SEV & PROI question in interview:) Many thanks.

#79 KNR

Well Done……..Very nice information………Many thanks.

#80 vashim

1- dead line
2- alfa beta testing done
3- test cases completed with certain percentege pass
4 – bug rate fall bellow certain level ltm
5 -functionality reaches to specified point

#81 MANZOOR

any one can explain about the concept test metrics

#82 How Are Issues Handled in JIRA? – Atlassian JIRA Tutorial #2 — Software Testing Help

[…] Priority:  This field can take one of the following values. […]

#83 Amit Sharma

very helpful information

#84 Failure Mode and Effects Analysis (FMEA) – How to Analyze Risks for Better Software Quality & Satisfied Customers! — Software Testing Help

[…] Severity of the failure (S) […]

#85 geetha

severity: Impact of bug on application.it will be assigned by testers.
Priority: which bug to be fixed first.
based on the priority,developers fixes the bug.

#86 Suman

Hi All,

I have query,

Company Logo Missing : Can we say it as high severity ?? Because missing company logo or mistake in company name will affect business. We can Say anything which affect the Business is high Severity. It also affect the business. But as per functionality, Its working fine.

Can you please clarify this.

#87 Prash

Suman
This high priority!!

#88 Srikant Kumar Biswal

Thank you guys for the first time i’m impressed with this descent discussions. Cool go ahead!

And thanx! Abhijit .. a way to go!!!!

#89 Srikant Kumar Biswal

Hi Pavani, here you go…

For Defect Metrics..

This is a document it should be prepared for knowing then and there the status or direction of a particular projects:

I iteration or Cycle: By tester team
=============
Total # of test cases :
# of test cases executed:
# of test cases failed:
# of defects reported:

After developers fix and confirm..

II cycle or Iteration by testers
=============
# of defects reported on I iteration:
# of duplicate defects:
# of Invalid defects:
# of defects fixed:
# of defects verified or closed:
# of defects reopened:
# of new defects:

…..like wise the iterations will go on till all the bugs has been fixed. But remember if the no of iterations goes on increasing then its a loss in both ways!

This may help you :)

Srikant,

Leave a Comment