priority and sevirity depens on the application , just for
example take a ok labelled button. if in GUI point of
testing say if the label name ok is labelled as Ko but it
does the functionality what it has to do so here we can say
this as High Priority and low seviratiy because it has low
impact on the system....if you are testing the same
application in UI testing the the same KO butoon has High
Priority and high seviraty...if you test in the functional
part the KO button has low priority and low seviraty...but
in cosmetict issues it has low priority and high
seviraty .....
for ex the company label appears to be wromg(VIRTUSA
appears to be VIRTUAS) actually it is a low priority
but many people accessing that site causes worst publicity
so ir is high severity bug
Pjstalin
[Lambent Technologies]
i cannot understand anwer which u hav posted , plz do
replyt again .....here is my mail
id ..vivek.ranganathan@gmail.com
i dont agree with sunil reddy that bcoz..as it comes to
company label ..if it is wrong it is given top priority
but severity is low bcoz it is a cosmetic error
we always focus on customer usage and client's business
needs,while assigning priority and severity.
Sometimes cosmotic and very minor functional bugs go under
high priority,where severity is very low.This will be
possible, only when the bug is in the most usaged page by
the end users and the page is most usagable for clien't
business.
Sometimes major functional bugs go under low priority bugs
(Not all times).This will be possible,only when the bug is
not in the most usaged page by the end users and the page
is not much usagable for clien't business.In this case,most
of the times this kind of bugs will defer to further
versions.
As per my exp ,most of the times all high severity bugs go
under high priority bugs.
Comments Please......
ex-login form accept any word,you will give high priority
and low seviarity.the database encripted field is not
encripted the expected format u will give high seviarity
and low priority.
I'll give u one example of high pririty and low severity :
Consider a job site which accepts resumes...in different
format say wrd,txt,html,pdf etc..
All is wrking fine but If u upload resume in html format
the apps hangs..
So its a high severity bug..
But Suppose: Mostly ppl upload in wrd,txt or pdf format and
chances of occuring the problem is say .1% so it can be
low priority bug..or at the most it can be planned to fix
later with giving a msg :ONly resume in wrd,txt,pdf format
is allowed to be uploaded.
So its typical case..but mostly high severity bugs are high
priority..
Priority: Means how soon you want to fix the bug to be
fixed.
Severity: Means how bad the bug is.
When setting a priority and severity, priority can be
comestetic error which gives the bad reputation to the
company. Severity is set based on the work around. If there
is no work around then it is set be a high severity bug.
priority&seviarity will be giving by testlead and some
times TE also depending on impact of bug on that
application how fast it will be solved.GUI related bugs are
coming under high priority bugs because........
{for excample you are customer,what do you see first ?
graphic related items and monitering items,right?.if you
saw the mistakes on first look what do you feel!. thats why
GUI related bugs are comes under high priority bugs.}
If bug impact is very high on the build then the priority
is high and it should solve as fast as possible.if the
impact is low then it can solved slowly.
Priority is Business, Severity is Technical.
High priority and low severity: In the application if there
is a spelling mistake in the login page it wont affect the
functionality anywhere but this we give high priority to fix
this issue, severity is very low.
High Severity and Low Priority: For example in a school
software there is a show stopper error in Examination module
that affects the application not navigate anywhere, but the
examination is going to held only on May, eventhough the bug
is very severe we give low priority to fix it.
if bug is found & we will know the main Resion for that bug
Arrise
1 - Corrective & Prevention Action
2 - Risk ana
3 - Root Cause analysis
4 - Impact analysis
In V model how will you explain all testing types
(unit,integration,sysetem,acceptance testing) as all these
parallel testing.E.g.Once the design phase is completed how
will you do the integration teting over here as tester
doesnt know much about design.Briefly justify the V-model?
If U have Test Cases already prepared and u have to just
excute those test cases in a very short time then how will
U decide which test cases has to be excuted first. Is there
any technique ?
recently, i attended for one interview. in that they asked
for project explanation. i explained that project. after
that they ask me to write test scenarios for that? in real
time i don't know how to write test scenarios. can any one
please write test scenarios for the following given project.
Health care solutions
This project mainly deals with Hospital Management System.
There are different modules, each module contain different
functionality. They are Appointment Scheduling,
Registration, Visit & Admission, Out & In Patient Service
Management, Lab Management, Bill Handling, Patient Notes,
Blood Bank, Master Setup & Security Module, and Pharmacy
Quotations.
Currently iam working in a small concern as a test
engineer, i have 3.6 yrs exp in manual testing, currently
iam looking for other concern, but some my friends saying
that testing is no longer, plz switch over to designing,
but iam interested in only testing, i want to know whether
the Testing has a boom or not? plz guide me
Did you received any Funny E-Mails from your Friends and like to share with rest of our friends? Yeah!! you can post that stuff 
Site Map
