Can You Tell Me About Bug Tracking?
As a QA Manager / Consultant I must have been asked hundreds of times which Bug Tracking Application I recommend.
If only life was that simple.
Answer a question with a question
This kind of question triggers two thoughts usually:
“Are they looking for free advice and support? Arghh!”
Putting aside the whole freebie debate for a moment, the second thought and usually my question back to you is,
“What platforms are they developing in and for?”
It’s Just Bug Tracking. Good Grief!
Isn’t it? Maybe not…
- Are you developing for the web, mobile or an actual Desktop Application?
- Is your product for Windows, Linux or MAC / iOS, Android, Windows Phone or Blackberry?
- If it’s Web which browsers and platforms are you supporting?
- The answer to these will probably define if you are using Visual Studio, Eclipse or other Development Environments
Some Bug Tracking solutions are not equipped to provide you with support if your product is being developed on more than one of these.
Bug Tracking Must Be Painless Productivity
If you are spending more time managing your Bug Tracking or if it duplicates your Customer Support Issue Tracking or cannot speak to your Source Control, Project Lifecycle Management or Test Case Manager then you are making your own life more difficult, more painful and being a lot less productive.
The key phrases here are: -
Web, Web, Web! Whichever you choose make sure it has web access for adding and viewing your bugs, whether you opt for a hosted solution or an install in your domain.
Real Time Collaboration: You want your Bug Tracking to allow your QA to interact and report issues with real-time notifications.
Integration: You want your other Development and test tools to be able to integrate seamlessly with your Bug Tracking.
Usability: You want to be able to setup and run the Bug Tracking and if need be make changes to configuration later.
Scalability: Build for success! Assume you are going to be growing as a company and will need to be able to scale your tools and not have to replace them. Having to migrate your Bug database to a new tool because you have outgrown the free or cheap tool you took a year ago can be painful and costly. So why do it?
The Warptest POV
Of all the Bug Tracking solutions I have worked with two stand out depending on your needs:
If you are doing all your development exclusively in and for Microsoft technologies, you are most likely using Visual Studio and the bright sparks at Microsoft realized several years ago that most development like this is done by teams. These teams were using Visual Studio, SharePoint and Microsoft Project so why not combine these to create a collaborative, task driven Lifecycle Management tool.
TFS offers some degree of support cross-platform including Linux, Android and iOS and it can connect to Eclipse for some functions.
TFS does all this and allows you to manage your Test Cases and Bug Tracking through a really nice web interface.
JIRA is probably the hottest Bug Tracking on the market today and delivers all of the key requirements listed above and is platform agnostic to boot.
Atlassian, JIRA’s parent company offers a slew of their own and 3rd Party tools that work hand-in-hand with JIRA in managing the Product Lifecycle.
IMHO these are your two best options. Both factor in not just technologies but also methodologies being applied (e.g. Agile). As for the price-tag both are affordable based on number of users so before you jump on that free Bug Tracking option remember,
“If you pay peanuts, you get monkeys”.