Alex Rivera | Logout

Bug tracking methodology

Asked 2010-01-05T14:39:07.490
10

I'm working on software for a company that doesn't ever file bug reports, the only complain, "so and so isn't working." Sometimes I can figure out what they're talking about, sometimes not. My pleas for screenshots and more details fall on deaf ears (once they did take a screenshot, then printed it out, scanned in it with their fax machine and emailed it to my boss as a TIFF).

I have several methods inplace to give me the data I need. Here are the steps I've taken:

  • A bug tracker in which they can enter bugs (only one was ever entered)
  • Error logging. Every time an error occurs, it writes it to a log file, courtesy of NLog
  • Program has a try catch around it's initial method to record exceptions.
  • When an unexpected exception is caught I take a screenshot of the program.
  • Access to all forms are logged, and to some extent, what they're doing. (although this usually only works if they succeed)

What other methods can I employ to allow me to catch bugs, and gather more data about them so I know how to reproduce them?

Edit
Report

1 Answer

3

If you have bug-tracking software, use it. Even if you're just entering the information your users tell you, it's a start. Tell them that bugs cannot be fixed without details of how to reproduce. Also, all your colleagues and testers should be using the bug-tracking software themselves.

answered 2010-01-05T14:50:39.233

Your Answer