4 ms·

I prefer the question. Saves me having to ask what they think it should do. "X doesn't work" often isn't very useful feedback in my experience unless accompanie

• draugadrotten 7y ago
  You're highlighting that good bug reporting is also a learned skill. It is not sufficient to say button X isn't working. An experienced bug reporter will also include information on what the expected behaviour was, and often also explain what is needed to reproduce the problem. It helps to explicitly ask about this from end users when you have a bug reporting form.
  • loopz 7y ago
    Except it's never learned. Most devs and testers absolutely suck at it, no matter how much training or long experience. Otherwise great people, but you need to put yourself in the role of the person receiving the bugreport. Most people don't know the tech too well, can't do that or forgets to do it very quickly. In the heat of the moment of deadlines, this is expected human behaviour, ie. optimizing locally. I find, when there's no common context, I have to reach out and spend some time with the person anyway. Usually you gain new insights, relationships and improved common understanding. Feels almost humanizing and well worth the time spent.