An argue is raised between a QA engineer and a Dev engineer about whether supportdump should be provided for any single bug.
I think this is one of the perfect examples reflecting the relationship between QA and Dev. Each side has its own interests, while meanwhile each side has to think of interests of the other so that both side can have a better life.
Following is my reply mail.
================================================================
Basically, I think
both of you are kind of “钻牛角尖”
Theoretically, as Joe (Dev big boss) mentioned,
“All
bugs must have a supportdump”, but chances are it could be unnecessary and ineffective for QA when a supportdump will not
benefit fixing a bug, in that case time is wasted in capturing and uploading supportdump.
So my opinion for
QA to handle with this issue
is “be practical and flexible”,
If you are very sure that supportdump
isn’t needed, for example a
GUI layout problem, just file a bug without
supportdump.
If it’s a server side bug
or, you are not so sure, file a bug with
supportdump, remember supportdump will never do harm.
If you have made a
wrong judgment and Dev
comes to you asking for
supportdump, just make one then upload it, no argue as Dev, not QA, is responsible for and capable of
fixing the
bug.
I personally
don't like there is a rule or something everyone has to obey, I believe in for over 95% cases QA and Dev can come to a same judgment regarding if a supportdump is
needed. I think this is so-called harmonious in our team :)
