Sometimes my QA team reports bugs, but neither I or them have any idea on how to reproduce them. This leads to very long and frustrating debugging sessions which sometimes do not even yield results.My software is tied heavily with proprietary hardware so bugs can come from many directions at once. Should I expect more from them than your software crashed when I pressed a button or should I figure myself what happened?EDIT: One of my coworker pointed out that we are probably all developers here so the results might suffer a little bias
Should QA find reproducible scenarios?
testing;bug;qa;reporting
QA should always try and make the bugs as easy for you to reproduce as possible and the bug description should contain the steps taken.However, if they can't easily reproduce the bugs, they should still get entered into the bug database with suitable title/headings and a full description of what they did to cause the bug.  The bug description should clearly state that they can't reproduce the bug (perhaps with some comment along the lines of tried it five times, it happened once).  This way, if someone else sees the same bug, they can add to the bug database with their findings and also you get as much information as possible which further down the line could be vital in saving you time tracking down the problem.Also, you get to filter the information - there might be a lot of bugs in different systems that you know are all linked to (eg) one area of the code - if QA don't report anything (as they can't reproduce them) then this information doesn't get to you.