The bug fixmanifesto

The purpose of this document is to promote good practices in bug fixing.

The preparation

The bug, the problem, in your system should be documented. It should be described somewhere. No matter if you are the developer that will work on it or the tester that found it. Create a ticket, issue, card, or whatever you use for managing your projects. Don't rely on instant messengers for bug reporting. Emailing is a little bit better but still not the right way to go.

Here are few things that you have to include in your report:

Get the things done

Now you have a nice bug report and can't wait to start working. Check out the steps below to make sure that you are on the right track.

Finish line

When everything is done and you are proud of yourself take some time to document your work. It takes just a few minutes but it matters to the reviewers. While submitting your changes list the following:

Happy bug fixing

Fork me on GitHub