Sign up ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

Are there any good articles or videos available that developers could use to learn to create more informative bug reports?

Often times I have to verify cases that were opened by developers where the title is the only information available, so I would like to help the devs become better bug reporters for both our benefit.

share|improve this question

closed as off-topic by durron597, gnat, GlenH7, Ixrec, MichaelT May 21 at 2:09

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions asking us to recommend a tool, library or favorite off-site resource are off-topic for Programmers as they tend to attract opinionated answers and spam. Instead, describe the problem and what has been done so far to solve it." – durron597, gnat, GlenH7, Ixrec, MichaelT
If this question can be reworded to fit the rules in the help center, please edit the question.

2 Answers 2

This page is very popular:

How to Report Bugs Effectively

From the introduction on the page:

Anybody who has written software for public use will probably have received at least one bad bug report. Reports that say nothing ("It doesn't work!"); reports that make no sense; reports that don't give enough information; reports that give wrong information. Reports of problems that turn out to be user error; reports of problems that turn out to be the fault of somebody else's program; reports of problems that turn out to be network failures.

Available in English, Português, 简体中文, Česky, Dansk, Deutsch, Español, Français, Magyar, Italiano, Nederlands, Polski, Русский & 繁體中文

share|improve this answer
Screenshots, screenshots and screenshots. It's really important to see the bug report visually, especially in the web development. Usersnap is a great tool for bug reporting. – Gregor Aug 21 '13 at 13:08

I have used the following list with testers and developers several times, and it improved bug reports, at least for a while afterwards...

In short: clear title, one bug per report, steps to reproduce, expected vs observed, screenshot

share|improve this answer
That one is easier to read ;) – user2567 Feb 9 '11 at 20:09

Not the answer you're looking for? Browse other questions tagged or ask your own question.