I have just join the company as the QA manager and I am looking for ways of improving our defect tracking methods.
We are using Bugzilla as our defect tracking tool and we have a lot of bugs which were not reproducible therefore stayed open in Bugzilla.
i am looking to find a procedure in which i can run it on these bugs and detemine at the end of it whather to close the bug or to leave it open and change it's status/sevirity.
can someone please help?
If it is not reproducible, is it really a defect? For example, if your company made automobile tires and one tire failed a manufacturing inspection, do you really have a defect in your manufacturing process that needs to be run down? Or do you simply monitor for additional failures?
If the answer to the defect question is no, then what you should do with the "defect" is obvious.
If the answer is yes, then you must decide your corporate policy on how to deal with defects that cannot be reproduced.
I know how I would deal with this situation, but I do not work for your company.
That's what the tester has to do.
Find out the bug make sure it is reproducible and get it fixed.
you have tell your team member(who has entered the bug)to try to reproduce the bug with their best.
try to create the same situation and find weather reproducible or not.
and even after trying so hard and unable to reproduce then you have change the status to obsolete.
To put things more clear: first thank you for your help.
The problem is really when you have a case in which for example the bug is reproducible only 5 times out of 15 so obviously we do have a problem only it is not consisitant, so what do you do in this case? you close the bug? you leave it open with a non reproducible note? and if you have 50 bugs like that in your bug tracking tool you leave them forever like that? is there any procedure of handling such cases?
If the bug reproducible 5 times out of 15 then surely you can't close the bug.
You can at least show this issue to development team and tell them this is not happening every time.
Let them check why this is going wrong.
and my opinion such bug can't be closed with non reproducible note.
If you unable to reproduce for single time then u might be closed with non reproducible note and with Risk.
It's sure you can not mark the bugs as not reproducible.
And even you should take action to put them in front of developers so that they will look what things are wrong. Atleast going through the code will give them some hint where the code is going wrong or where it can be.
Take developer with you, tell him to sit back with you. Do the bug reproducing process 15 times. Show him the bug is occurring atleast 2 times. It must be fixed. Developer will also get the exact idea of the bug nature.
You can not change bug status in such cases. You must pay attention to fix them as early as possible before shipping the code. Also see the severity of that bug, if not sever and you can not figure out the reason mark it as differed.