Answer / praveen mehra

Severity and Priority Difference:



Severity: Depends on the impacts of defects [Impact of bug
on the functionality of application].



High/Critical: System Crash, Unable to access/navigate some
of pages/modules, Unable to save valid data, Server error
occurrence frequently. [“Without resolving the defect we r
unable to continue testing.”]
Medium: Bug causes major functionality or other severe
problems. [“Compulsory to solve but able to continue”]
Normal: Control Alignment, Wrong error message display,
improper error message, typos etc…
Trivial: Any suggestion bug you can put in trivial
severity.


Priority: It defines “How soon the bug should be fix”. Mean-
How important is it to the business that we are fix the
bugs.



· High (Critical): Must fix as soon as
possible, the user will reach this scenario in the very
first experience.
Medium: Validations related, Control alignments (UI
bugs),Spelling mistakes [Should fix before the product
release]
Low: Any suggestion bug. [Will fix if time left or might be
postponed]

Answer / shankar

Priority defines the importance of defect w.r.t. client
point of view i.e. how soon it should be fixed.
Responsibility of Development Head. Classification could
be: Urgent, High, Medium, Low

Answer / ap

Assigning Priorities is a tricky business and shall always
differ depending upon the nature of the project and the vie
type of the person deciding.

Most projects however shall see an initial priority being
assigned by the tester, which generally are open to
modification by the dev teams.

in all cases priorities vary primarily from Critical to
Optional, semantics and synonyms change obviously.

Micro View: Execution Part:
For a tester, assigning bug priorities are commonly based
on pre-set guidelines/documentation.

Even for a developer assigning a priority at a developers'
stage, it will be rigid in terms of following protocol,
Effect mapping, response time etc...

Macro View: This is basically the part when bug priorities
are intervened in by QCs/TLs/PMs/ Delivery Managers etc...
Coming to this point, extrenal considerations like Time To
market, User Feedback, mass aplication usage repurcussions,
ROI etc. kick into the picture and the priorities are re-
assigned keeping in mind the broader picture

Answer / praveen mehra

Hey I am totally disaggre with Deepthi as priority and
severity depends on each other as per her comment. I
request to every visitor please ignore that comment posted
by deepthi.

Please consider the points mentioned by me if you still
have any confusion regarding priority and severity then
incase you can mail me.


Thanks!
Praveen Mehra

Answer / rajendra

Hai Naz,
Priority will be assined by developper and not by
tester based on how Severely bug affecting the application
performence.
For example if the defect/bug is a show stopper i.e
it causes to hang to system and not permitting to test
futher then the developpper must resolve it very quickly.

Here the prority means how importance is given by the
developpper to resolve/correct it.

priorities are

4.Immediate
3.Later
2.Whenever time permits
1.next version

Here NO 4 priority is top level one which indicates that,it
should be resolves as early as possible.

In some companies priorities will be indicated with 0 to 4
or 0 to 3 or 1-5 numbers.

ok then byeeeeeee
friendz,
Rajendra Prasad reddy
rajendra_penumalli@yahoo.com
Hyderabad

Answer / deepthi

Defect Priority means importance of defect.Based on defect
seviarity , we give Priority.
Highest priority will be given to critical seviarity.
Moderate priority will be given for major seviarity.
Low priority will be given for minor seviarity

What is Trivial Bug?

2 Answers  

what are testing types involved in black box and white box testing...

1 Answers   PCS,

What are the Level of Severity

11 Answers   Atlantic Scientific, Deloitte,

What is smoke testing and user interface testing ?

0 Answers  

How to explian the V model. Diagram not required but iwant the answer gnerally No Diagram explanation plzzzzzzzzzz..

2 Answers   Accenture, TCS,

What is the purpose of a test completion criterion? What is the purpose of a test completion criterion? a) to know when a specific test has finished its execution b) to ensure that the test case specification is complete c) to set the criteria used in generating test inputs d) to determine when to stop testing

0 Answers   Nucleus Software,

Could you please give me an example of test scenarios for online banking testing (like billing,payment,statements etc.) (like how to test the functionalities of Payment module, Billing module...etc.)?

2 Answers   HP,

Explain Water fall Model

7 Answers   ITC Infotech,

What testing procedure you follow? how

0 Answers   RBS,

what comments have u given in peer review? tell me at least 3 comments what u have given? july27 brahma412@yahoo.co.in

2 Answers   CTS,

what type of bugs u found commonly in ur project?

3 Answers   Wipro,

What is regression testing

4 Answers   CMC,