What is Pesticide Paradox?

The pesticide paradox is the testing principle that running the same set of tests repeatedly eventually stops finding new defects, just as pests develop resistance to a repeatedly used pesticide, so test cases must be regularly reviewed and revised to remain effective.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

IN DEPTH

In depth.

Coined by Boris Beizer and one of the seven principles of software testing (ISTQB), the pesticide paradox warns that a fixed test suite has a shelf life for discovery. Once your tests have found the bugs they can find, re-running them only confirms those areas still work; they will not catch defects in untested paths or in new code. The suite still has value for regression, but its bug-finding power against new issues plateaus.

The remedy is to keep evolving the tests: add new cases for new features and risks, revise existing cases, introduce different techniques (boundary analysis, exploratory testing, new data), and review coverage so you are probing areas the current suite ignores. Exploratory testing and varied test data are common antidotes because they deliberately go where scripted tests do not.

The principle also tempers the idea that "more passing tests = higher quality." Passing the same tests forever says little about the parts of the system those tests never exercise.

WHY IT MATTERS

Why interviewers ask about this.

The pesticide paradox is a classic ISTQB and interview topic. Citing it, and explaining the fix (review and revise tests, add new ones, use exploratory testing), shows you understand that a static suite loses bug-finding power and that quality requires continually evolving coverage.

EXAMPLE

Example scenario.

A team's 500 automated regression tests pass green for months, yet users keep reporting bugs. The tests cover the original features well but were never updated for new functionality. Recognizing the pesticide paradox, the team adds cases for new areas and runs exploratory sessions, immediately uncovering defects the static suite could never find.

TIP

Interview tip.

Define the pesticide paradox as the principle that repeating the same tests stops finding new bugs, so suites must be reviewed and revised. Name it as one of the seven testing principles and give the remedy: add and update tests, vary data and techniques, and use exploratory testing.

FAQ

Frequently asked questions.

How do you overcome the pesticide paradox?

Regularly review and revise your test cases: add new tests for new features and risks, retire or update stale ones, vary test data and techniques, and use exploratory testing to probe areas scripted tests ignore. The point is to keep the suite evolving so it continues finding new defects.

Is the pesticide paradox one of the seven principles of testing?

Yes. The ISTQB lists it among the seven principles of software testing, alongside ideas like "testing shows the presence of defects, not their absence," "exhaustive testing is impossible," and "defects cluster together." It specifically addresses why static test suites lose effectiveness over time.