Sara Williams - What makes for a good bug report?

Sign in to queue


Sara Williams, head of MSDN, talks about how to write a great bug report. MSDN, earlier this week, turned on the MSDN Product Feedback Center, which is where you can report (and look up) bugs in the next version of Visual Studio.





Download this episode

The Discussion

  • User profile image
    Sounds a lot like what suggests for bugzilla use, and good advice for any bug reporting effort.
  • User profile image
    Quite common sense, like good advice usually is. Have to see if the code editor selection rendering/gfx corruption bug is still around in beta1. It happened often and always seemingly randomly, sometimes it also disappeared suddenly. Trying to tell the repro steps for that one is a pain as I couldn't figure any common action I did before it came.
  • User profile image
    Tom Servo
    The problem with listing repro steps is that internally they're using newer builds than us beta testers. And I've seen it a couple of times in the Office 2003 beta that my repro steps didn't work for the developers, because changes in the newer builds changed the way slightly to reproduce it, so I had a bunch of bugs that had to be reopened after a beta refresh.

    So depending on what's reported, I'd expect the developers to take at least a quick look at the responsible code section, hoping for some "Doh" moment.
  • User profile image

    When I worked in PSS, I wrote a KB article about how to submit bugs. It's directed at VFP users, but the principles should apply to any language.

  • User profile image

    yep - you can't always repro.

  • User profile image
    Not exactly - sometimes, the bug still happens in the current build, so the repro steps still work.  If that doesn't work, we do keep the current public build available so that we can look at the issue you report.
  • User profile image
    Deactivated User

    Comment removed at user's request.

Add Your 2 Cents