:: 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 (5200)
 Manual Testing interview questions  Manual Testing Interview Questions (6477)
 QA Concepts interview questions  QA Concepts Interview Questions (655)
 Mobile Testing interview questions  Mobile Testing Interview Questions (113)
 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)
what is defect clustering and pesticide paradox?
 Question Submitted By :: Manual-Testing
I also faced this Question!!     Answer Posted By  
# 1
The ISTQB define 7 testing principles, two of them are:

Defect Clustering, which means that some modules may
contain most of the defects discovered during pre-release
testing, or are responsible for the most operational
failures, which means focusing on the most defected area.

Pesticide paradox, means you need to updates your test s
after repeating over and over again, because eventually the
same set of test cases will no longer find any new defects.
Is This Answer Correct ?    64 Yes 4 No
Samer Desouky
# 2
pesticide paradox:
Pesticide paradox describes a common problem in
exterminating bugs -- both the 6-legged and software

Insects that survive the use of pesticide are those that
are more immune to the poison than others. These bugs'
offspring are then also likely to be immune to the
pesticide. This requires that pesticide companies
continually work at developing new poisons that will kill
whatever survived their previous products.

The same occurs in software. If we create bug prevention or
testing processes that tend to prevent and find particular
types of bugs, other types of bugs will thrive because our
attention is focused elsewhere. Also, designers,
developers , and testers are likely to learn from their
mistakes and not make the same mistakes again -- they will
make new ones. This causes scripted testing -- whether
manual or automated -- to become less effective over time.

Good testing requires continual development of new testing
ideas. Old regression scripts can be useful but testing
should not stop there. Regression tests will not find the
bugs that are lurking off the beaten path.
Is This Answer Correct ?    43 Yes 13 No
# 3
defect clustering:
Joe made the point clear, density has got nothing to do
with clustering. Yes, yuva could have meant "higher
density" but even then that is not what is "important"
about clustering.

Many things in the world reflect the "principle of factor
sparsity" and Software Testing is no exception. For
example, in two dimensional arrays used in most programs,
we find that they are sparse. Let me make it simple here-
long ago, an Italian economist named Pareto highlighted
that 80% of Italy's wealth was owned by 20%. From then
onwards it has become a generic tool of conclusion, and was
applied to many things of the world we live in.

There exists a hypothesis (with a reasonable amount of
reality in it) that bugs are typically clustered in one
area. Something like 80% of the defects being present in
20% of the overall codebase.

So, when you hear that an application has 1000 known bugs
and look at the detail of their distribution, many of them
perhaps originate from 20% of the modules therefore forming
a "cluster of defects".

If you were to buy this principle, then you have to start
thinking of where you can apply this- one example would be
to suspend testing if you sniff a cluster (instead of
finding all the rest of the defects, perhaps an upfront
alert from the testers could make the developers seriously
review that portion of the app again in a hope to fix the
found + about_to_be_found defects). This requires
speculative intelligence and is risky, though there is an
engineering endorsement to the principle. Another example
would be (in case where the project is over and the test
summary information is available for post-mortem), one
could do a thorough Root-cause-analysis on the cluster.

And so on.

Ashwin Palaparthi
Is This Answer Correct ?    26 Yes 12 No
Ashwin Palaparthi
# 4
Defect Clustering: Finding more defects in one particular
area (or)in one functionality. The reasons Might be (1) Lack
of dev Experience (2) poor Requirements (3)Several Defects
are fixed by many developers to same functionality (4)
Fixing of new defect can cause new defect in the same

Pesticide Paradox: We need to updated our Test Cases as
executing the same old test cases will no longer produce new
Is This Answer Correct ?    2 Yes 2 No
# 5
Defect clustering is a testing principle which can be stated
as : Number of modules which contain most of the defects
discovered during pre-release testing is small.

This paradox states that running the same tests over and
over again would not show any new defects because all
defects found using the initial test cases would eventually
all be fixed.
Is This Answer Correct ?    4 Yes 8 No

Other Manual Testing Interview Questions
  Question Asked @ Answers
Who should test your code?   2
what is version 1   11
What is the difference between QA and QC? Millennium 8
what is tracebility matrix? what is negative testing RTG 14
I have one doubt in regression testing, Example if we have five modules such as 1,2,3,4,5. If we made change in 3 module only and also 3 module will interact with only 1 and 5 module. For this case we will conduct testing in all module (or) only 1 and 5 module?? Answer soon firends   2
What is the Difference between Stub Testing and Driver Testing? CTS 9
About Testing Methodology?   5
What is Traciability Matrix Airbee 10
When priority and Severity is opposite then which one required to solved first? Bug Number 1=(Severity 1 & priority 3), Bug Number 2=(severity 3 & priority 1), (high=1,Medium=2,Low=3) Hp 2
what are the differences between stub abd the driver ? CA 5
what kind of bugs you can find in the application in manual testing?   1
What is confirmation testing? Different between regression testing, confirmation testing and unit testing?   1
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.   ::