Creating a Bug Tracker | Secrets of the Game Business (Game Development Series)

What do you need to start a bug-tracking database? You can talk to several vendors who sell software packages that can do the job. If you have the money and are short on time, this can be a good way to get started. In most cases, however, you can save money by doing it yourself with a simple database using SQL or Access as the front end. It's even possible to make a simple tracking system using a spreadsheet or e-mail based system, although this type of system would not be as flexible.

Begin the database creation by outlining on paper what you want your bug entry form to look like. From there, you can determine what is required in the database fields. You would want to include areas for the date and time the bug was found and the version of the program in which the bug was found. Include areas for a description of the bug, the steps to reproduce the error, and any other special notations about the specific bug. It is highly recommended that you include an area for saving metadata such as log files or screenshots. Anything that would help the programmer replicate and understand how the bug was created should be included on this form. In fact, try to get feedback from the programmer about what is needed on the form during the creation process.

Case Study 4.7.1 contains a sample bug report form.

Case Study 4.7.1: How to Report Bugs

Your Company Name: ________________________ Bug Number: _________

Reported by: ________________________________ Assigned to: __________

Status: (Open/Closed/Hold)	Priority to fix: (High/Low)
Program: _______________	Version: _____________
Error Type: ________	Severity: _____

Programming error1. Fatal

Design issue2. Serious

Art3. Minor

Database

Hardware

DirectX

AI/Scripting

Documentation

Attachments? (Y/N)

Description of problem:

_____________________________________________________

Steps to reproduce:

_____________________________________________________

Resolution: ________ Fixed in Version: __________

Fixed

Hold

Not able to reproduce

Not fixed due to design

Not fixed due to other restraint

Withdrawn by tester

Need more info

Comments:

_____________________________________________________

Resolved by: ___________________ Fix Tested by: ________________

Once you have a rough draft on paper, you can quickly identify the database fields needed to store the information. Just by using the Wizard interface in Access, you can easily turn this form into a powerful tracking tool. It is also important to remember that a tracking tool is only beneficial if it is used consistently. Unless your team members use the tool daily, it will quickly become worthless. It is the quality assurance manager's job to ensure that no one treats bug tracking lackadaisically.