Defect Clustering And Pesticide Paradox

Defect and Pesticide are the two principles of testing.

Definitions:

Defect Clustering: - The condition when we inspect most of the bugs in the small number of modules, and face the most operational failures.

When tester finds the most of the bugs in the small part of the application then it is called defect clustering.

Pesticide Paradox: - If the same number of tests repeated again and again, then same test cases will not find the same number of new bugs. This is what pesticide paradox refers to

Overview of the Defect clustering:

Defect clustering is what it is the no of defects testers find out on the smaller part of the application or the when tester reported the maximum number of defects in the smaller part or module of the application.

When defects are not scattered on the whole application rather on the smaller part or in some module of the application then it is refer to the Defect clustering.

Basically defect clustering is know as when we inspect or find the bugs in the application and among the bugs most of them are from the same part of the module.

It is based on the Pareto principle, also known as the 80-20 rule, where it stated that approximately 80% of the problems are caused by 20% of modules.

Overview of the Pesticide paradox:

After Number of iterations of testing number of bugs get reduced, as developers become more careful to those areas where testers found more defects and might not look into other areas.

After a certain number of iterations hence, by executing the same test cases will no longer help to find more defects, because those reported defects on that areas are already get fixed by the developers, so we need to make new text cases to take or to see new scenarios on the application due to which testers can find the bugs to make the application bug free, so in the Pesticide paradox made new test cases to cover all the uncovered scenarios of the application.