Avoiding the "Test and Test Again" Syndrome


Conference for the Association for Software Testing (CAST) 2007


2007 Conference for AST

CAST 07/2007

I’ve heard that a frog won’t jump out of boiling water if the water is slowly heated from room temperature to boiling and the frog was placed in it before heat is applied (which I tend to believe without needing to test it for myself). It seems that a frog does not react to slow changes in temperature, even when its life is threatened.  Some test projects I’ve worked with seemed to have gone through a similar process; the test team came in one day and realized that it was time for the final testing push, but they had been so busy running tests  that they hadn’t had time to prepare properly. The test team had become embroiled in what I call the "Test  and Test Again Syndrome." What are some of the forces behind this? What does it cost us? How can testers successfully deal with the Syndrome? How might it be avoided? What are some of the approaches that have failed to deal with it? The session delves into some of the lessons learned through the school of hard knocks.

Presented at 2007 CAST

Avoiding the Test and Test Again Syndrome (Abstract) floppy disk
Avoiding the Test and Test Again Syndrome (Slides) floppy disk
Avoiding the Test and Test Again Syndrome (Paper)


5620fada351f3