I hate answers like this
on 06.16.05, 06:59am in software • comments (3)
I had a buddy in college who would always hack up a bunch of software and try to get his friends to run it. Without doubt, 9 out of 10 times the software would crash, do something totally unexpected or just simply do nothing. His reponse was always the same: "Works on my machine"…
Well duh, of course it does. But it’s a crappy answer.
It’s the same thing when I see bugs resolved as "No repro", "not our bug" and of course my least favorite, "works on my machine".
Obviously, it doesn’t happen on your machine - but I bet you it’ll happen on an end users machine. Grrrr.
Brian Hampson (June 16, 2005 @ 9:26 am)
“No repro” is a brutal problem. I hate it when I can’t, or my users can’t reproduce the bug again. I know it’s lurking deep within, looking to bite me in the @ss when I’m least ready
Randy (June 16, 2005 @ 9:43 am)
You’ll appreciate this then… I submitted a bug yesterday that automation picked up accidentally. Since it was an odd set of steps - in the middle of the script no less - I took some time to duplicate the error by hand and used those steps in the bug as the repro-steps, as any tester should.
Late last night the bug came back as “No Repro” - this morning I ran through the exact same steps on a newer build to see if newer bits fixed it… ya know, trying to have a benefit of the doubt moment for the Dev.
Not only does the bug repro on the newer build but it crashes as well, meaning that the original error is probably a lot more serious than I had originally thought.
(Excuse me while I have a small moment in the tester-dance-of-joy)
jr (June 17, 2005 @ 7:47 pm)
lol “works on my machine”