there-is-always-one-more-bug

Michael Bolton at DevelopSense blog says that a significant question for software testers is:

“Is there a problem here?”

Great question for testers. In a thought exchange, one of our clients said “I am a firm believer in the fact that however long we test, there-is-always-one-more-bug. As a testers, it is very crucial for us to know where to draw a line. Obviously, when we complete a test cycle, there should be no show stopper but there-is-always-one-more-bug lurking somewhere in the application. It is the same “there-is-always-one-more-bug” theory that pushes a tester to think differently, to think beyond what an analyst or designer thought and challenge the system.”

I believe that combining the quest of finding a bug (“Is there a problem here?”) with “there-is-always-one-more-bug theory” can work wonders for software testers in coming out with findings no one in the project team would have ever thought of.  I believe it is these findings that differentiate great testers from average ones.