benefits BlogRoll tools

Bug Tracking Tools Explained

Like it or not, all software has bugs.You may not know about them but they are there..lurking in the darkness, ready trip up one of your innocent user who has just gone and purchased your software.
That’s why you employ a software tester. A software tester’s job is to find as many of the bugs and report them to you and the rest of the team before they can do untold damage to you and  your software’s reputation.

You can report bugs in as many ways as there are to communicate. You can write the bugs up in an email, on a piece of paper, in a spreadsheet (see my previous post on spreadsheets). You can even directly speak to the relevant person and directly show them the bug.

Or you can use a bug tracking tool.

So why do you need to track a software bug and whats so great about a bug tracking tool?

Software Bug Workflow

Well, just as a normal bug goes through several stages in its life such as egg, nymph, larvae and finally adult, so to does a software bug go through its own lifecycle or workflow. Redmine the opensource software I use as my online bug tracking tool,  uses the word workflow so I’ll use that term in this post.

Typically a simple bug workflow goes as follows:

Bug WorkFlow


new is when a tester creates a bug report

open is when a developer  accepts the bug report as valid

fixed is when a developer indicates that the bug is fixed

tested is when a tester indicates the bug has been tested

closed is when a tester accepts the bug has been fixed and the report is now closed

This is a very simple workflow. Alternatives to the workflow can happen when for example,  bugs are rejected by the developer  or a bug fails test and the tester places the bug back to open state. In fact, it can get quite complicated if you let it.

Most bug tracking tools will let you modify or create your own stages and workflows, but if your new to the concept of a bug tracking tool, its better to select a simple existing workflow and use that for a while to get used to what works for you. Redmine, lets you chose a preexisting work-flow.

A bug tracking tool then allows a tester to create a bug report and monitor its progress as it goes through its workflow

So whats the big fuss? Why not just use a spreadsheet or email?

I’ve personally benefited a lot from bug tracking tools. Here are some ways they’ve helped me.

Benefits of a bug tracking tool

1) Its easy to keep track of one bug, but keeping track of many bugs is hard work. A tool helps you easily find out what bugs are still open, fixed, closed. Bug tracking tools normally allow you to sort and filter your bugs and create reports on the bugs.

2) You can track other stuff about bugs, such as how important they are and who is fixing them. This can help you prioritise which bugs are important and require urgent fixing.

3) You can start seeing clusters of bugs which indicates there may be underlying issues in parts of the code

4) Lots of people can see the status of the bugs, not just the tester and the developer. The overall bug status can be quickly reviewed by many avoiding nasty surprise syndrome (NSS) at the end of development/testing.

5) Sometimes not all bugs are fixed in the current release but will be fixed and tested in a future release. This means long after software release the bugs still need to kept open and tracked. A bug tracking tool ensures that these bugs are not overlooked in the future.

6) A bug tracking tool can centralise information. Often a bug tracking tool can be used to track new features as well as issues and can act as a document repository. Redmine offers many additional features such as document repository and wiki.

7) A bug tracking tool can improve productivity by increasing bug awareness and responsiveness. It is also handy when a project is scattered geographically and works across different time zones.

As I’ve mentioned in previous posts, there are many open source options bug tracking tools out there, so if budget is an issue there is no need to spend a lot of money on an top end commercial tool.

And of course, a tool is only as good as the developer and tester using it and will fail miserably if no one is willing to use it, so perhaps if your thinking of adding such a tool to your testing toolbox, speak to the rest of your team first to find out what they are looking for in a tool.

15 replies on “Bug Tracking Tools Explained”

Nice post. I like the benefits of the bug tracking tool you’ve outlined, but I especially like the way you put the ownership firmly with both the tester and the dev.

I’ve seen too many test teams purchase a bug tracking tool only to find that the devs don’t like it. It’s a team tool. 🙂


Great post. We couldn’t live without a bug tracking system, but there is another important user as well as dev and testers. The product manager (i.e. the chap who decides what features will be in the product). Whenever a bug is raised you need to make the decision when it will be fixed. Is it critical (current release) or not. In some cases this is obvious (the system crashes on startup) but in many cases it isn’t (the sign in mechanism is less usable on one browser). Most products have a large number of bugs to start with; it’s important that you fix the ones your customers will care about first and get the product out there. In the bug tracking system, your product manager can review all the bugs and decide which are the key ones from the customer perspective. That’s not always obvious to developers or testers. I’d agree if you have more than 1 person in your operation, a bug tracking system is a must.

Good one, I liked the last couple of lines of this post.
I have seen that the Project Mgmt team always tend to
have these complex workflows and validations within the tool hoping to generate fancy reports out of this tool.

I have never seen it achieve it’s purpose, it’s always backfired.
A bug tracking Tool is best used to track defects, nothing else.

Keep it nice and simple, that’s the Mantra.


Would you also log defects during unit testing?

If I was a developer I would only log a bug if I needed to keep a history of the problem. For instance, if for some reason i was unable to fix it immediately, or unable to locate the issue, I might write up a bug report. In time, I would perhaps see a pattern that would help identify the cause of the problem.

Leave a Reply

Your email address will not be published. Required fields are marked *