:: Home Page            
 Advertise your Business Here     
Browse  |   Placement Papers  |   Company  |   Code Snippets  |   Certifications  |   Visa Questions
Post Question  |   Post Answer  |   My Panel  |   Search  |   Articles  |   Topics  |   ERRORS new
   Refer this Site  Refer This Site to Your Friends  Site Map  Bookmark this Site  Set it as your HomePage  Contact Us     Login  |  Sign Up                      
Categories >> Software >> Testing >> Manual Testing


 Automation Testing interview questions  Automation Testing Interview Questions (5206)
 Manual Testing interview questions  Manual Testing Interview Questions (6496)
 QA Concepts interview questions  QA Concepts Interview Questions (656)
 Mobile Testing interview questions  Mobile Testing Interview Questions (115)
 Test Cases interview questions  Test Cases Interview Questions (469)
 Test Documents Reporting interview questions  Test Documents Reporting Interview Questions (58)
 Testing AllOther interview questions  Testing AllOther Interview Questions (609)
Pls give examples for 
1.  High severity and high priority.
2.  High severity and low priority.
3.  Low severity and high priority.
4.  Low severity and low priority
 Question Submitted By :: Manual-Testing
I also faced this Question!!     Answer Posted By  
# 1
Hi everybody what I found is there is a little clarification
needed for simple concept of severity and priority.severity
shows the impact on the application which can be high or low
like system crash will have high severity.while priority
denotes how much it is important to fix the if system
crashes once in say 150 times then it will have low priority.

so examples for these are below:-

1.High severity & low priority :- If a application crashes
on very rare occasions and changes are very low of severity will be high but priority will be low.

2.High severity & high priority:- if a application crashes
very frequently and duly visible or first time the
application came from development team to the testing

3.Low severity & low priority:- it is merely just a
enhancement bug which the client wishes like changing the
background colour of user interface,also like adding a
button like 'back' to navigate previous page.

4.Low severity & high priority:- In this case if the name of
the company on its home page is misspelt will be considered.

So to find that in which category the bug comes always
remember one thing that Low severity bugs are mostly related
to GUIs and high severity bugs always related to things like
system crash.severity is always technical while priority is
for business purpose.
Is This Answer Correct ?    29 Yes 3 No
Akhil Kumar
# 2
H-P H-S – Login id & Password Encryption is not done at
client Side
H-P L-S – Company Logo is mismatch
L-P H-S - Session is not expiring after clicking on logout
button in
any screen.
L-P L-S - Client Side Validation for text box & Field
Is This Answer Correct ?    20 Yes 7 No
# 3
A good way to clarify this may come from the so-called
"Failure Mode Effects Analysis" process in quality Management.
A triad of Severity (S), Occurrence (O) and Detectability
(D) produces a so-called "risk priority number" (P).

"S" - "How much money do we lose if this happens".
"O" - "What ratio of business processes are affected?"
"D" - "Can we find out in time if the defect occurred?"

If S is high, but O + D are low, then P is low.
If S is high and O + D are high, then P is high.
If S is low and O + D are low, then P is low.
If S is low and O + D are high, then P is high.

S high, O + D low:
Once a year, the database must undergo housekeeping or
tablespaces will one day overflow, crashing the entire
system, denying every business process until the tablespace
is freed and the application restored. Unfortunately, the
script does not work.
This is a very high severity defect.
This is very easy to detect (monitor tablespaces) and will
not occur quickly (a year down the line) so the priority is low.

S high, O + D high:
The corporate SOA "swallows up" fire-and-forget requests for
a certain constellation of parameters.
As you cannot know when a request got lost, you do not know
when or which business processes may fail.
As such, the priority is very high.

S low, O + D low:
The "undo" functionality of an application produces a
warning message when no change has been made prior to
execution. This irritates the user as "no action" or a
grayed-out button would be preferred.
Other than that, there is no business impact.
As such, there is a low priority: The developer might fix it
when by chance they are updating the module, otherwise no
sane project manager would waste budget on a fix.

S low, O + D high:
This is the typical scenario of "Defect with Business
processes unaffected".
The "Help" function from a portal sporadically causes the
servers to crash.
(There is a very easy workaround: just don't use the "Help",
and therefore people can still commence every business process.)
Something, however, still needs to be done, and that
quickly. An easy fix may be to disable "Help" - but you just
can't go live with that thing!
Is This Answer Correct ?    3 Yes 1 No
Mike K.
# 4
High severity and high priority:
suppose an applicaton crush after start.

High severity and low priority.
In start up window application name or spelling is wrong.

Low severity and high priority.
suppose a database needs to be updated monthly but it gives

Low severity and low priority
A scrolling button is there at the frontscreen.
Is This Answer Correct ?    17 Yes 30 No
# 5
High severity and high priority.
application crash

High severity and low priority.
spelling mistake on homepage
e.g missing h in

Low severity and high priority.
Session is not expiring after clicking on logout
button in
Low severity and low priority
spelling mistake not on homepage
Is This Answer Correct ?    2 Yes 18 No

Other Manual Testing Interview Questions
  Question Asked @ Answers
After fix the bug if requirement change the tester what will do?   1
What is Software Testing ?   4
what id test effort Estimation in testing ?   1
what is difference between regression & retesting?   7
Suppose that your're running tests on the windows calculator and find that 1+1=2,2+2=5,3+3=6,4+4=9,5+5=10 and 6+6=13. Write a bug title and Bug Description that effectively describes this problem? FCG 9
When you were testing an application, you found a strange pop up with a “500 internal error” and you thought to log it as a defect. Give description of the defect along with all the details you expect in the defect content   1
What are the common problem of software development process?   1
How can we explain about matrics..Every time iam getting this question..Have you involved in metrics??..Plz..plz Can any anybody give the sugessions..What is the best way to explain about metrics..give me your valuble answer..thanks in advance...   3
how many test cases are posible to write on textbox. but it is allows the 0-10 digits numaric CTS 2
who is responsible for QA and QC? AMDOC 5
What are the Challenges you faced while testing your Projects CitiGroup 4
How do we analyse a bug?   4
For more Manual Testing Interview Questions Click Here 

Copyright Policy  |  Terms of Service  |  Articles  |  Site Map  |  RSS Site Map  |  Contact Us
Copyright © 2013  All Rights Reserved.   ::