if suppose there is a road accident the people who went
into serious condition will give high priority and hight
seviority.
in functional if suppose there is a customer meeting about
the project, the simple things like spell check of login
screen etc will have the high seviority and high priority.
susmitha your answer general in nature i don't want
road accident like examples.
I want realtime s/w related answers.
Please try to provide that type of answers.
Suppose there is an application which gives some banking
related reports weekly, monthly, quarterly & yearly by
doing some calculations. In this application, there is a
fault while calculating weekly report. This is a high
severity and high priority fault because this fault will
hamper the functionality of the application immediately
within a week. It should be fixed urgently.
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.
Ajaya still you are beating around the bush
what you said above is corporate data securiry.I am juest
asking you about fuctionality related defects and high
priority and hign severity defects example
please give me proper answer
one example i have, like when u click on setup file for
install the software but as u click on setup file its crash
ur system. plz tell me if i m wrong and if u have more
example send post them
darshan.testing@gmail.com
Just take an example of online banking application login
screen if you are entering correct username ans wrong
password .... it should not accept you to access ,if it
accepts ...we can say this as high priority and high
severity ...it depends on the functionality ......as
well as the application .......
i hope iam right if not plz correct me .
Thank u .
i am not agree for the above answers,Its major issue
in the application, its varies from complex functionalities
in the application. for example , some functionality having
major issue crashing the application and it faces more
number of customers or enduser(say 100+people) then its
comes under high priority from the customer prospective,
and high severioty from the business impact prospective.
so developers has to fix immediatetly. i think it's clear.
-by Wipro technologies
for example,we can consider the GUI defects as minor
defects with low priority, but during a demo to the
customer we need to consider this minor as major and should
give high priority. and fields validation can also be
considered as major with high priority based on the
customer requirements.
Please correct me if iam wrong.
All the run time Errors and calculation Errors comes under
high priority and high severity
i.e When u r unable to move further in your application, no
work around is possible then it comes under high priority
and high severity.
suppose for example when u are testing any financial
application and that is accepting -ve data and all the
transactions are resulting in -ve values then we can say
this is of high Priority and high severity.
If iam wrong pls correct me.
Hi...
Here we'll consider an ex of a data base mgmt s/m,
when we edit a customer data, automatically it should
overwrite the existing data base..but if it creates a new
record.. it affects the functionality of edit, and this
kind of error is considered as high severity and priority
IF the bulit is ready for release, and there is a
functionality to save the data into the page but when we
click on the save button then application as crashing and
not able to save it
then we can this type of bugs as High severity and High priority
High priority and high severity deines that, How much above
bugs are affects our s/w.
tester T/L only to decided that how this bug is affectt.
suppose, we have a calculation s/w and the button of (+)is
not to working correct or not shown total amount after
additon. then t/l has to decided that which type of bug and
how it affect our s/w.
severity has to be major or minor depends on Bugs.
Priority has low or high depends also on tester T/L or
developer.
None of the answers meets the requirements. The query is to
have the real time examples which can give the clear picture
about the differences about the HP & HS. Can any body let me
know, if a defect is of High Priority then why should i also
mention it as HS. If anybody can answer it to the perfect.
Please review the answer below :
High Priority : Suppose while testing the portal If I am not
able to save the data, then it is high pririty defect need
to be fixed , since its an important part of the portal.
High Severity : In case if I am not able to save the data
due to which there is a big impact on the portal flow and
more number of requirements are being affected then tester
will mention it as High Severity defect.
Case study like you have been assigned in a team which going
through a crucial phase of the project. Then how you can
save your project to release on time without any defect
leakage….
What actually you(Testing) people do when a new project
starts. i.e can you give clear idea how testing is
integrated with Project development &Release