Migration and Synchronization b/w HP Quality Center, Microsoft TFS and MTM

Migration and Synchronization between HP QC , TFS and MTM 

Kovair Omnibus platform provides seamless Migration and synchronization between HP QC, Microsoft TFS and MTM. It supports migration of all HP QC elements (Requirements, Bugs, Test Cases, Attachments, History and Links between items) to TFS and their interrelationships and facilitates execution of QTP Test Scripts linked with Test Cases from MTM. 

Thus, Kovair brings value to Team Foundation Server and Test Manager users who also include HP tools in their development process. The solution works with TFS 2013 and HP QC10 and QC11.

What can one achieve from QC, TFS and MTM integration?

• Unified TFS repository for all ALM assets - Requirements, Project Management, Development, Test, Build
  and others
• Full collaboration between Development and QA teams
• Centralized reporting from TFS
• Easy and flexible configuration
• Execution of QTP Test Scripts linked with Test Cases from MTM
• Complete support of Manual, Automated and Load Testing from MTM
• Direct viewing of QTP Results from MTM

Watch this Kovair Video on Migration of HP QC elements to TFS and MTM.

Download video

Key features of Kovair Omnibus for QC, TFS and MTM integration:

• Complete support for Call 2 Tests
• Mapping of QC Requirements Folder Structure to TFS Area Path for Requirement tracking
• Mapping of QC Releases & Cycles to TFS Iterations
• Migration of QC Design Steps with Parameters and Default value.
• Bidirectional synchronization of Requirements, Defects, Tests, Steps and Test Scripts along with their interrelationships
• Support for migration of History Data , RTF Fields and Attachments
• 100% web interface for codeless configuration of integration rules

Example Scenarios

Scenario 1:

The development team works on TFS as their collaboration platform for automated software delivery and the QA team is migrating from QC to TFS and MTM. In a typical case for larger enterprises, the migration cannot take place overnight and both the tools need to run in parallel for some transition time.

Scenario 2:

The development team works on TFS as their collaboration platform for automated software delivery and the QA team works on QC and wants to continue with QC for Defects, Requirements and Test Cases. The two teams continue to work on two separate tools and they need to be in sync to increase efficiency and reduce delivery time.

Scenario 3:

The development team works on TFS and the QA team works on QC and wants to move to TFS, but would also like to use the existing Quick Test Professional (QTP) scripts for automated testing.

Contact for consultation

To gather more information about the Omnibus solution please visit this page  and read the press release.

To understand how this migration from HP QC to TFS and MTM can help you using single TFS repository for all ALM assets , email us or schedule a demo. We would be happy to provide you with the right solutions. One may also call us at 1.408.262.0200 Extn. 1 to schedule a live demonstration.