The Old Joel on Software Forum: Part 4 (of 5) - Testing Software

Testing Software - Which to Use?

We are currently using a SQL Database
with an Access front end for our bug tracking and we have outgrown it.
FogBugz looks promising as a replacement. However, our CEO is evaluating
testing tools as well and most of them have or sell bug tracking
components as well. In particular, he is looking at TestDirector and,
having read several of your opinion pieces, I was wondering if you might
comment on two things:
1) How does FogBugz compare to TestDirector's bug tracking mechanism?
2) What should we be looking for in a testing tool?
Thank you for your time and attention,
Simon K

SimonK
Monday, February 2, 2004

I'm curious why your CEO is evaluating testing tools. Shouldn't your lead developer be doing that?

Norrick
Monday, February 2, 2004

Maybe the CEO outsourced everybody and there is no one left to evaluate things.

m
Monday, February 2, 2004

Or the company is small enough (and fortunate enough) not to have an HR department.

Nigel
Monday, February 2, 2004

Look at the process you want to operate and then buy a tool which helps you.

Do not buy a tool and create a process around it.

If you can't work out the process then you're going to end up in a mess whatever you do so get someone in to sort out your process for you.

Think of the interaction between your bug management process, your change process, your release process and your helpdesk processes. These all need to be integrated.

Process, process, process.

gwyn
Tuesday, February 3, 2004

We are small and each have many, many hats. CEO is also in charge of the testing effort. Nevertheless, the point of the question is to provoke a discussion of the testing tools that are available. Such as Test Director. Which is very expensive, but is is worth it?

SimonK
Tuesday, February 3, 2004

What are your requirements?

gwyn
Tuesday, February 3, 2004