Originally posted on my blog:
https://www.dowen.me.uk/it-works-on-my-machine/
So, you just found this great bug and it's returned "cannot reproduc...
For further actions, you may consider blocking this person and/or reporting abuse
The developers' team is always on the defensive mode with the QA and that the relationship between both works well depends on the context of the situation. As a developer, it has happened to me, however, I believe that we should always try to find solutions to problems and not resort to the typical phrase "works on my machine".
One thing I believe that helps without much bureaucracy is having the QA as part of the team itself.
Frequently we see a QA Team that is responsible to test code from other Dev Teams.
What I really like is a cross-functional team that includes a QA inside it. This improves communication, ownership, empathy and avoid "passing the baton".
indeed, this is generally the way I've worked for a number of years. It still has not stopped me having to spend a fair amount of time dealing with the underlying causes of "Works on my machine". But it has meant a more friendly and collaborative partnership with the Dev's while I do it.
For all but the most basic websites, environment/platform are mostly non-trivial and can easily throw up the unexpected difference from running locally or in a Dev env vs "Test/UAT/Prod". And I've used docker extensively, it just means the discrepancy is hidden in some .yaml configuration :)