Bug Tracking Tool
Work in progress

or Why it is not possible to manage any software development without a bug tracking tool

A bug tracking system is basically a database linked to  a frontend:
  • The frontend can be a FAT client, understand a windows or application running on your pc and that need to be install by each developer/client, or may be
  • Adhering to a light client server model: HTML frontend which submit queries to a server.



When was the bug open, and closed, what is its status now. Who has reported it (login is required and all system support profile (user, tester, manager, developer, administrator) and/or isolation of project). Did It already existed in a previous version (regression in code), etc...


 Easily dispatch responsability or find quickly who was reponsible for solving it, how  much time was needed to close this bug, some system may send email automatically to developer to inform them... etc...


How difficult will it be to solve this issues, (can be a bugnote add by other developer). Most of the time, technical leader decide of the value of this field together with developers.


How many bugs are still open at a date "t", how do I determine the order in which I will solve them...etc

Standardisation of records

By forcing tester/customer to enter some mandatory fields in a graphical forms. It may avoid You to hear some ridiculous statement like: "the application is not printing, working". It force the user talking a language You have decide together, having agreed on a "bug category" list is a very good and common example.


All modern bug tracking tool let You define and customize some part of the system according to your need.

Addition of information

A screenshot is better than thousand word, a file create by the application, a memory dump, anything that will help developer to reproduce the bug.


A lot of very powerful queries can be executed. It is always interesting to know, how many improvement were done in the next/past releases, or if a team has use more power to develop new functionnalities (also changes request which interest the customer the most) or loose time tracking some low level bug priority.
In case of reporting, Bugzilla support the following:
  • Tabular reports - tables of bug counts in 1, 2 or 3 dimensions, as HTML or CSV.
  • Graphical reports - line graphs, bar and pie charts.

Al of the above will have a positive result on:
  • communication among the team of developers and customers,
  • It will improve the product quality by several magnitude,
  • Developer will be more productive as the will know what to concentrate on or what is worth to do.
AND Your customers will be happier!!

Golden rules

  1. A bug that can be reproduce can be analysed/corrected.
  2. Correcting a bug is not always trivial, a correction may introduce new bugs.
  3. The intrinseque quality of a software is always improved with a tracking tool over time

Some open source software:

Bugzilla (http://www.bugzilla.org/) is the more famous, use in a lot of open source application (Mozilla, Apache, and even eclipse) version 2.19.2 (MySQL+PHP, Solaris, Linux, Win32, MacOS X, BSD) 370 companies are currently using it. (Nasa, IBM, Mozilla and others)- Wikipedia has a very brief article on it, Features are listed here

Mantis. (http://mantisbt.sourceforge.net/) A very simple bug tracking tool with limited search functionnality compared to bugzilla, a strong community but not so much stable release as expected.

Buggit (http://www.matpie.drw.net/PBSystems/products/buggit/Buggit.html) no new release since 2000 and bounded to MS access, aka running only unde windows. Listed Here because I use to play with it in 2001.


You might like also

Top 12 Reasons to Write Unit Tests
Most programmers do not write tests. We all know that we should write them, but for whatever reason, most of us don't. This is unfortunate, because testing is the most powerful tool we know of to improve software quality. Tests reduce bugs, provide accurate documentation, and improve design. Read the Top 12 Reasons why You must also try to convince your colleagues …
4486 Days ago
No Thumbnail was found
Still hesitating about using or not using regression tests in your code? (JUNIT for java for ex.) Look here at Failed fixes haunt credibility of Microsoft's Trustworthy Computing Initiative. Even Microsoft has some problem today...because they do not have invested enough time/money/power into it.... …
5442 Days ago
No Thumbnail was found
Jester - the JUnit test tester: Jester changes your source code, recompiles it, and runs your bunch of JUNIT test suite to see if anything breaks. It help the developer to verify if enough, or better the most iimportant testcases are already written...more at IBM developerWorks, do not forget to also read or reread JUnit Test Infected: Programmers Love Writing Tests essay.A comprehensive unit-test suite is a necessity for a robust program. But how can you be sure that your …
5458 Days ago
No Thumbnail was found
Open-source ITP - Powerful web application tester ITP is a deceptively simple, yet powerful web testing harness. It is a stand-alone #Java application that can test your website from a user's perspective. It is amazingly simple and lightweight, yet can be used for powerful test-scripting by using building blocks to create large test runs. ITP is the fastest test harness software to learn. A test script is simply made up out of a few lines of XML. There is no …
5539 Days ago