Severity: Impact of the defect on the Application. Assigned
by Testers.
Priority:Impact of the defect w.r.t users.
: How fast we have to solve the defect.
severity describes seriousness of the defect with respect
to functionality
where
priority describes importance of defect to solve with
respect to customer.
Severit: how bad the defect and its reflect or imapact on
the s/w application with respect to the customer
requirement and on the user.severity given by the test
engineer.
Priority: How important the bug when it is to fix.It
shopuld be fixed on the basis of importancy of requirement.
Priority of the defect decide by the Developement team
member.
I can differenciate with example
suppose we identify two bugs
1. The client logo is not appearing on the web site but the
site is working fine... in this case the severity is low but
the priority is high because from company's reputation it is
most imp to resolve. After all the reputation wins more
clients and projects and hence increases revinue
2. The Qaurterly statement event is not triggering from the
website and we are just at the begining of the new quarter
after a new release.
In this case the Severity is High but priority cauld be low
becase we have time till the quarter ends to fix the bug
So the botemline is that in the priority v/s severity
matrix the priority is completely bussiness impact driven
and the severity is completely technical impact driven. :)
Hope this helps !!
the diff will be more clear if u go for an example of Low
priority high severity and high priority low severity
1. low p high s :- suppose we have a link on our site that
is visited very rarely may be in once 1000 times on which
our system crashed that is High Severe because whole system
crashes but Low priority because Link is very rare.....
2. misspelled company name or missing logo from front page
have no impact on s/w functionality but having a worst
impact on company's goodwill so this is this case of high
Priority but Low severity........
i hope u will understand...
Severity:Severity indicates the criticality of the
failure[Functional or procedure failure of the complete
system with no work around, or defects that are urgent
customer care driver].
Priority: The order in which the defect should be fixed.
Manual Testing:
1.How do we categorize Test cases in Regression Testing?
2.How can u do Performance tESTING?
3.What r the parameters u apply for doing functional testing?
4.what is non-functional testing?
5.if they r more number of test cases how can u pick up a
selective test case?
6.what is good requirement& bad requirement?
7.what is functionality testing?
8.how to manage test cases when requirements change?
9.at what phase of project testing starts?
10.diff between test bed n test environment?
11.what did u achieve being a tester?
12.what is pare to analysis?
13.what is testcondition? who prepares it n when it is used?
14.what is show stopper?
15.what is backend testing using sql?
16.diff bet application testing n product testing?
17.what is cause effect graph?
18.how performance testing done manually?
19.what is proto type testing?
20.pre UAT and UAT testing?
21.
what is broken link in web testing n how to test it?
22.what is cyclomatic complexity explain with example?
23.what is buddy testing?
Hi everyone.This is one of my interview questions.Could you
please send me the answer for this?My ID:spam4rekha@gmail.com
Q : what is BVA and ECP ?
Thank You
rekha
Condition testing is a control structure testing technique
where the criteria used to design test cases is that they
Option 1 Rely on basis path testing
Option 2 Exercise the logical conditions in a program module
Option 3 Select test paths based on the locations and uses
of variables
Option 4 Focus on testing the validity of loop constructs