As a 'Developer' I expect these qualities from 'Software Quality Assurance Engineer'

This topic depicts one of the legendary fights between developers and Quality Assurance Engineers over one and foremost issue which is actually a reported bug, but if an individual or fresh minded person drill down the synopsis behind this fight, one would find a simple problem that triggers the overall fight and which is ?? Technical expertise.

Many developers now a days argue about QA engineers not having any technical expertise of the project yielding towards reporting bugs that have no significant importance. Now I have personally seen this behavior or you can say fight but didn't know the actual root cause behind it, thereby after some elevation in my years of experience in software testing, I closely observed developers beef against QA engineers which were mainly highlighted as no difference between User experience and technical bugs, proper steps of reproduction and video recording.

Why developers argue about known difference between UI and functional? When QA reports a bug related to UI and report it to developer instead of UI, developer first insists QA to report it to UI instead of developer with proper explanation of the bug, but it is the resiliency of the QA to ask developer about fixing it without wasting any time. Now here developer expects QA to actually debug the main source of the problem via browser debugging tool or any other alternative just to see if its actually related to developer. The second thing that developers argue is the proper steps of reproduction. Many of the reported bugs have direct steps that sometimes stir a confusion in developers and causing developers to prolong the duration of the bug by adding comments after comments before respective QA engineer. Third point which developer specifically mentioned was video recording. There are many bugs which are reported do not require steps of reproduction rather than complete proof of bug which can only be done via video recording.

Now what can be done to ease down the concerns of developers for QA engineers. One can think of effectively inspecting the element by noticing if some UI misalignments have have occurred, if yes, properly mention the tweak required in expected result and report it to UI. The other thing that can help developer reproducing a bug is proper explanation of the bug which you can facilitate either by writing down the entire journey in the form of steps OR you may detail your bug description. The final thing which can also affirm your bug is video recording which would be directly helpful for developers. Albeit there are other alternative ways that could eventually end the quarrel but keeping the above mentioned things in mind will help developers and QA engineers aloof from any unexpected quarrels.