Obvious Bugs

 

After a series of good quality delivered to the customers, there came the temptation to short-cut testing activities. Under pressure, trade-off decisions have to  be taken. Can we risk delaying the release again due to a weird anomaly that happens from time to time while we have no reproducible scenario at hand? Is it better to start investigation and communicate the bad news to the release manager? What if we ship anyway? Will the testing department look bad if customers find obvious bugs like low hanging fruits? We've gone through all of this, but one lesson we have learnt is to raise a ticket for all anomalies, regardless whether we have a reproducible scenario yet. The meaning is to label our internal findings as known anomalies/findings and ship this information along with the release notes. As soon as we have a reproducible scenario, we extend the ticket accordingly and the product owner can plan the fix. If it turns out to be a flash in the pan, good; and if not, at least, we are not in the line of fire. We found the problem, before the customer did.

(Source: Simply the Test)