How to manage two separate testing teams using different test tracking tools

Posted by newuser on Super User See other posts from Super User or by newuser
Published on 2013-10-22T15:11:11Z Indexed on 2013/10/22 15:57 UTC
Read the original article Hit count: 343

Filed under:

bug-report

I have two independent testing teams currently testing the same application. One team is using ClearQuest, and the other is using Mantis. It has been a huge effort to manage all of the duplicate reported bugs. What options would improve this situation? My constraint is that the ClearQuest team will not change test reporting tools. The migration to ClearQuest also comes with a large training effort.

Related posts about bug-report

I have a stacktrace and limit of 250 characters for a bug report

as seen on Programmers - Search for 'Programmers'
I'm developing an xbox indie game and as a last-resort I have a try...catch encompassing everything. At this point if an exception is raised I can get the user to send me a message through the xbox however the limit is 250 characters. How can I get the most value out of my 250 characters? I don't… >>> More
Best practice for marking a bug as resolved in Bugzilla ?

as seen on Programmers - Search for 'Programmers'
I am wondering what is the best way to handle the situation of marking a bug as resolved and providing a version of component/product in which this fix can be found. Context For a project I am working on, we are using Bugzilla for issue tracking, and we have the following: A product "A" with a… >>> More
Is it a bug or a task when something doesn't work, yet, in development process

as seen on Programmers - Search for 'Programmers'
We usually have this dilemma in our team. Sometimes, in order to implement a task or a story we find out that the system must be in a specific state. For example, a specific system configuration has to be made beforehand. The task / story can be completed and it is working as specified on it with… >>> More
Is it good practice to analyse who introduced each bug?

as seen on Programmers - Search for 'Programmers'
I used to analyse performance of programmers in my team by looking at the issues they have closed. Many of the issues are of course bugs. And here another important performance aspect comes - who introduced the bugs. I am wondering, if creating a custom field in the issue tracking system "Blamed"… >>> More
Best practice while marking a bug as resolved with Bugzilla (versioning of product and components)

as seen on Programmers - Search for 'Programmers'
I am wondering what is the best way to handle the situation of marking a bug as resolved and providing a version of component/product in which this fix can be found. Context For a project I am working on, we are using Bugzilla for issue tracking, and we have the following: A product "A" with a… >>> More

Developer IT

How to manage two separate testing teams using different test tracking tools - Developer IT

How to manage two separate testing teams using different test tracking tools

bug-report

Related posts about bug-report

I have a stacktrace and limit of 250 characters for a bug report

Best practice for marking a bug as resolved in Bugzilla ?

Is it a bug or a task when something doesn't work, yet, in development process

Is it good practice to analyse who introduced each bug?

Best practice while marking a bug as resolved with Bugzilla (versioning of product and components)

Categories cloud