Quality Testing

Quality is delighting customers



I was just wondering how you deal with "not reproducible bugs".

I mean - I've seen many different workflows how to handle such bugs - but I was never quiet happy with it.


What did I see so far?

(+) Bug is gettin deleated by QA lead

(+) Product development refuses to bug & sends it back to QA

(+) Bugs remains in BugTrackingSystem and will never be fixed (dead Issue)



None of these "solutions" really satisfys me!

How do you handle such a situation?



Views: 629

Reply to This

Replies to This Discussion

1. As a precautious measure to this kind of bugs, screen shot can be taken for the bugs found!!

2. try rebooting the entire system, so that you can try the same scenario again in which you got the bug.


In the first scenario, I'd chat with the QA lead to understand their motivation. Was the bug deleted accidentally? Was it an invalid bug, e.g. the result of a tester's misunderstanding? Did the QA lead misunderstand the bug?

In the second scenario, I'd make sure QA and product development have a shared understanding of the bug itself: not its severity rating or its priority, but the plain facts about the context in which the environment in which the bug occurred, the actions that triggered the bug, and the bug's observed effects. Once you both agree on the facts, you can discuss whether and when the bug needs to be fixed.

In the third scenario, what dissatisfies you: that bugs that need fixing never get fixed, or that the bug tracking system is tainted with dead issues, or something else? My experience is that there is always too much work to do, so there are always problems that don't get fixed. If everyone's doing a good job, the dead issues are unimportant enough that it doesn't especially matter whether they get fixed, but no one has the time (or the decisiveness) to mark a dead issue was "something we'll never fix".

Finally, here's an important lesson I've learned in my career (it also applies to marriage): pick your battles. We never get everything we want, even if we're sure we're right.

document it, chat with testers/users, if someone saw that too -> collect information

when it occurs again the person should know that it's a bug and add all new information to the bug tracker.

when enough information is collected it might become reproducible.

important part is that everyone should know about it so there's no "I must have done something wrong, I'll ignore it"-situation

Hi Peter,

For the scenario -1) Bug is getting deleted by QA lead : Well this is something should not happen, but in that case QA lead should know the issue or the scenario how to reproduced.

2) Product development refuses to bug & sends it back to QA : In that case QA people should be confident to handle such kind of cases, they should be tried to reproducible in their env and can show the developer. That case is possible only if QA and Dev have different environments...

3) Bugs remains in BugTrackingSystem and will never be fixed (dead Issue) : That case is something related to development when any sudden change is suggested by Client. First time the issue is occurred in any module and suddenly client suggest some change in module due to which previous issue was not occurred. So as QA has reported that issue already in tracking system, but then development team said that it's not reproducible so could not be fixed. But from QA prospective as we cannot delete the reported bugs , it will remain as it in the system..

Peter I hope I 've cleared your queries at some level.




thx to all of you.

Got some good points to think about :)


TTWT Magazine





© 2021   Created by Quality Testing.   Powered by

Badges  |  Report an Issue  |  Terms of Service