In the software test, there is a phenomenon called the pesticide paradox (pesticide paradox), that is, the more software testing, then the software test personnel testing the more immune.
First, let's take a look at what the pesticide paradox is, the annual variety of harms to the fields and crops, and the agricultural experts to find the right way to fight and use the modified formula to design the pesticide.
But the pests adapted to the new insecticide and produced immunity. To invalidate the new pesticide. In the years that followed, the old insecticide was only used to kill immune-free pests, and at the same time it was necessary to introduce new and improved formulations to fight the more tenacious newly compiled pests. The combination of old and new pesticides sometimes hinders the effectiveness of old pesticides.
As time passed, the old insecticide became useless. As a result, pests and pesticides keep fighting and see who has the upper hand at last. Sometimes pesticides win, but sometimes pests can succeed in defeating the latest pesticides. The result of this struggle is the constant development of nature and pesticides.
In the software test, in order to overcome the "pesticide paradox", the test sample needs to be often reviewed and changed, and constantly add new different test examples to test the different parts of the software or system, to ensure that the test example is always up-to-date. This includes the last time the program code or the description document update information. In this way, the parts that have not been tested in the software or the previously unused input combinations will run again, thus discovering many other flaws. Software testers must constantly write new and different tests to check different parts of the program to find many other bugs. Letting other people test your program will help break the pesticide paradox.
Copyright notice: This article blog original article. Blogs, without consent, may not be reproduced.
Paradox Software tests Pesticides