How to track software bugs the spreadsheet way

//How to track software bugs the spreadsheet way

How to track software bugs the spreadsheet way

By | 2016-02-01T22:42:19+01:00 January 31st, 2014|Software development|0 Comments

These days you can get all sorts of software applications such as LighthouseGithubBugzilla or FogBugz – there are loads! to help you track software bugs – other popular definitions used are issues and defects.  Using a software application to track defects works great if you want to spend some money investing in a software bug tracking applications. And hope that the application doesn’t contain any bugs too!

I’m all for simplicity (remember KISS) and I’ve found that a good old fashioned spreadsheet works just as well and that a cloud-based sharing system such as GoogleDocs is an easy way to share and track spreadsheet changes.
The essential bug tracking items, which end up being your column headings in the spreadsheet are:
  • Date raised.
  • Name or initials of who raised it if there’s more than one tester.
  • Detailed description of the issue/bug.
  • Where in the application did the bug occur?
  • Has the issue been corrected/fixed?
  • Notes to track the bug which should have the commenter prefix their comments with their initials and a date eg. JKM: dd-mmm-yy.
  • Has the fix been verified? And if so, what’s the verified date.
You can easily move off verified items to a separate tab or add a Status column and filter the results on Open/Fixed/Closed.
It’s as simple as that, so there you go, it’s now time to track those pesky software bugs and squish them!

Leave A Comment