Wednesday, December 22, 2010

Random issues

 Have u faced random issues during testing? Testers look at the exceptions logged and try to find out the root cause of the issue. If they cannot find the root cause, they call in the developers. What if the devs are not able to find the root cause of the issue from the exception logs?

Here is the typical flow for such scenarios

Testers log the bug mentioning that the bug is random.
Two or three days down the line, a Dev team picks up the defect.Since he is not able to find the root cause from the logs, he marks the bug as not reproducible and moves it into QA plate.

QA tests it for two consecutive builds. Since he cannot reproduce the issue, he is forced to close the issue.

After a few months, the build is delivered to production, where the bug is reproduced.

Major showdown happens with client.

Few points

1. Neither the Dev or the QA is able to escape from this vicious cycle. Each is doing his best, but in the end - when bug occurs in production - its the proverbial mess -

2. No QA is able to stand up and say that since x number of bugs are critical + random, and since no code has been checked in to fix the issue, we should not ship the product.

So taking mass consensus before shipping the product ( a key characteristic I have seen in several agile projects ) is not useful here.