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

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.

In search of the ultimate bug tracking tool

As many of you know, I’ve been on the hunt for a bug tracking tool for a while now and I’m glad to say the hunt is over.

I needed this bug tracking tool to meet some key criteria.

1) It had to be easy to install. Startups don’t always have a reputation of up front planning and I wanted a tool I could recomend that was quick and easy to install.

2) It had to be open source. I didn’t want to pay for a bug tracking tool unless I had too. My clients feel the same way.

3) I wanted to embed the bug tracking tool into my website Testing Times and then provide it as a service for my clients who don’t have or want a bug tracking tool.

4) It had to be easy to use and secure. I wanted each client to have access to only their project.

TRAC got the heads up for being opensource, but was too hard to install in comparison to YouTrack, which beat it hands down. YouTrack only provided a temporary license though and I had trouble getting my hosting company to support Apache Tomcat. The effort to install something I may have to pay for later, made me feel it was pointless to pursue.

Tails was interesting and looked great, and if I had to pay for a tool, their pricing structure suited my needs. There is no messy install as it’s a hosted service but that meant that I wouldn’t be able to embed it onto my site.

Practitest had similar issues for me, and also the pay per month/user pricing structure didn’t suit my needs.

I was at a bit of a loss until BHARATH suggested Redmine.

Redmine is an opensource tracking tool that’s easy to install, easy to configure and secure.  It ticked all the boxes and it’s now sitting on my website. You can take a look at it at  http://bugs.testingtimes.ie if you like.

I have created a public project called Testing Times for those who want to investigate a bit further.

The real test of course will be my clients, their reaction and how much they use it.

So a hearty thanks to Bharath and a sigh of contentment from me.

YouTrack, a new issue tracking tool

I noticed that there is a new bug tracking application on the scene. It’s called YouTrack and describes it self as:

“web-based, keyboard-centric issue tracker” and

“The Fastest Bug and Issue Tracker”
“Wow”! Sounds like just the tool for a Maverick Tester!  I’ve been on the hunt for a decent bug tracker for my website, so I thought I would try this one out.

The download and install was true to its word, it was fast and immediately a login page appeared in my browser. Fantastic! I had spent many hours installing  TRAC and in comparison this was a cinch!


I’m now the proud owner of YouTrack on my laptop.

There’s a few things seem nice, one is the use of tags and the ability to create users under projects only, which will be handy for me as I don’t want my clients to be able to see other project content.

I did have a grin at the roles though, there was admin, developer (of course), observer (??) and reporter (?!). I think that we testers will fall under the “reporter” role.

This application is under Beta, and JetBrains are asking for people to raise bugs as they see it. Hopefully, the beta testing is a bit more successful than Joe Stump, of blundermove.com (see Elizabeth’s Hendricksons great  post on this).  Or  they have performed some solid system testing (by their “reporter” )prior to this beta release.

I’m going to try and install it on my web server in the next two days, and I intend to use it for a current client I have.

The major downside I see to YouTrack is the fact that it’s only a temporary license. I don’t want to invest large amounts of energy into a product that turns out to be excessively expensive. For startup’s TRAC or Bugzilla which is opensource may still be more worthwhile.

Anyone else used YouTrack?