| || |
New TD Installion - Setting w/o Defect Mgr
My team is currently setting up TestDirector for our company. We will be using our current defect tracking (a custom-built bugzilla), but we need to track the bug id # for any failed test case. So I am curious to know if anyone else setup TD with a separate (not integrated) defect tracking and how they tracked a bug identifier in TD for a failed test case/run. Thanks for your help.
[ 08-17-2005, 01:51 PM: Message edited by: lojeca ]
Re: New TD Installion - Setting w/o Defect Mgr
I think you'll find a broad range of integration out there, from basic to highly sophisticated. It all depends on the "openness" of the defect tracking tool, on the time an money an organization is willing to put on the table and, of course, on its business requirements.
Basic integration: defects are tracked in the external system and a batch job extracts defects data every night to feed the TD defects module. To do that, you just need to have a user-defined field in TD to hold the id of the bug in the external system (external Id).
One step further: when you need to link TD defects to test runs, you make the external Id field mandatory at defect creation time, i.e. one cannot enter a new bug in TD if it is not already in the external system. Data cannot be modified in TD but it can be used to create reports and graphs.
More sophisticated: replace the New Defect form with your own, that creates the defect in both systems. Then synchronize, on demand or at a given time of the day/night, the data in TD and the data in the external system. Of course, you'll need some API to the external system. This is basically what is done by the third party tool vendors when they provide an integration of their own.