Quality Testing

Quality is delighting customers

Can u tell me anyone how to give priority and severity in manual testing?

can u tell me anyone how to give priority and severity in manual testing?and how to install qtp trail version for android mobile application testing??????????

 

regards.

Anu

Views: 465

Reply to This

Replies to This Discussion

Hi Aruna,

Severity is nothing, its a degree of impact on the application, so depend upon the impact you can give the severity

for example s1,s2,s3.

for high severity like If not able to do the further testing and no work around then we will give S1

for medium defect and work around is there then we will give S2

for low defect  and work around is there then we will give S3

 

Priority is nothing, it a degree of urgency on the application, mean how soon want to fix the defect

for example

If not able to do the further testing and no work around then we will give P1,stating that it is very urgent

for medium defect and work around is there then we will give P2

for low defect  and work around is there then we will give P3

In some company tester will give only severity and in some company tester will give both severity and priority. its depends on the company.

We will give this severity and Priority in Bug tracking tool

 

With Warm regards,

Firoz

 

 

 

 

Hi Firoz,

 

thanks for giving valuable information.

 

  with warm regards,

   Anu.

Severity:

severity means how serious the bug is?

Priority:
  Priority means a message to the developer, what defect are taken first ,next and last for defect rectification.

BY

www.alligatortek.com

Severity - Impact [It can be High, Medium, Low etc.(varies with company) The selection should be based on the definitions established in the company. If impact provided is not according to the established rules proper justification should be given.]

Priority - Urgency [depends on the importance of the feature as required by the customer, normally taken in consultation with PL/TL]

severity means impact of the defect with respect to functionality point of view. it is given by tester

status in severity:

critical(showstopper)

high(eg like caluculation,functionality errors etc....)

medium(like boundaries missing etc...)

moderate(invalid poup messages,etc..)

minimal(usablity...)

priority : impact of the defect with respect to client point of view and how soon it should be resolved. it sis given by developer like p1,p2,p3,p3

Severity is the one which states how bad or critical is the bug..it is usually reported by the tester to the developing team....

 priority is the level which determines which bug needs to be fixed first...whether it is of priority high(first) or can it be resolved(not fixed in this release) or can it wait(low level)...it is usually determined by the developing team or the manager..

Hi,

Simple way of understanding the Severity and Priority



Severity:How a bug affects from the testing point of view

Priority:How a bug affects from the Client point of viewExample:If on the final round of testing u ve noticed that the logo of the client is wrong ...that is high priority and less severity...because u can continue testing the other parts of application it wont affect ur testing.thats y given less severity.but at that time it is a high priority bug because it is a major bug for the client.

At the same time the bug i mentioned will be a low priority bug and low swverity ...if the same occurred on the first round of testing

RSS

TTWT Magazine


Advertisement

Advertisement

Advertisement

Advertisement

© 2021   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service