Pesticide Paradox Software Testing

Pesticide Paradox Software Testing is when we test user specified requirement then defect will be finding at a large number in certain complicated area or flow of information. When we test same area again and again to find out and correct the defect, after some changes or modification or iteration there will be no longer find new defect even have.

According to Boris Beizer “Every method you use to prevent or find bugs leaves a residue of subtler bugs against which those methods are ineffectual.”

Developers should take care in those places where testers found more defects and might not look in to other areas and good tester requires continual development of new testing ideas.

By executing the same test cases for same area or critical area will no longer help to find more number of defects. So test cases need to revised or exercised in different way to find out defect.

It is important to review the test cases regularly and new different tests need to be written to exercise different parts of the software product or system to potentially find more defects.

Following are the methods to prevent pesticide paradox -:
1] Write test cases to execute the different part of the system.

2] Prepare new test cases after some iteration and add them in existing

3] Test all possible scenarios and functionality of application changes over time

4] Should take of critical places of modules or where imminent danger feels

Leave a Reply