ALM Data Migration and Synchronization b/n HP QC, TFS & MTM

This page highlights a few scenarios requiring a robust integration and migration solution between HP QC / HP ALM, Microsoft TFS and MTM. Kovair Omnibus Integration Platform along with the required Adapters for these tools can help organizations to effectively address these scenarios. The solution works with TFS 2013 and HP QC 10 and QC 11. 

HP Quality Center and Team Foundation Server HP QC to TFS and MTM Migration

HP Quality Center has been a popular tool for quality management during software development.

Microsoft Team Foundation Server is a complete Application Lifecycle Management product which provides for source code management, reporting, requirements management, test management and management of other lifecycle activities. This combined with Microsoft Test Manager (MTM) provides an alternate solution to HP Quality Center. As more and more organizations intend to make any shift of platforms the need for a robust migration solution is becoming evident.

Kovair Omnibus Solution

Kovair Omnibus platform provides seamless Migration and synchronization between HP QC/ HP ALM, Microsoft TFS and MTM.

Kovair Omnibus platform supports migration of all HP QC elements (Requirements, Bugs, Test Cases, Attachments, History and Links between items) to TFS and their interrelationships. The integration goes a step ahead and supports the migration of HP QC Test Cases along with automated Test Scripts to TFS as Generic Tests. The scripts get checked-in to TFS and allow the users to download it from TFS and execute it from MTM. This platform also facilitates customized configuration and mapping for any specific migration or synchronization use case.

 

What can one achieve from HP QC/HP ALM, 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

After migration, if both the tools are to be maintained, then Omnibus provides seamless bidirectional synchronization to keep the individual artifacts in sync in both the tools.

The idea of a single platform where individual tools coexist is a useful model for small to large organizations. Kovair recognizes this challenge and provides the solution for this. Omnibus platform allows best-of-breed multi-vendor ALM tools to coexist and work together in a unified software development environment.

 

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.

QC to TFS and MTM-Scenario1

Omnibus Solution:

This requires initial migration of data from QC to TFS followed by bidirectional synchronization of artifacts like Defects, Requirements and Test Cases between the two systems. Kovair Omnibus achieves this by providing an interface to configure and start the Migration between the systems. Kovair’s ESB based integration bus makes sure that the items remain synchronized even after the Migration is over.

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.

QC to TFS and MTM-Scenario2

Omnibus Solution:

This requires bidirectional synchronization of artifacts like Defects, Requirements and Test Cases between the two systems. Kovair easily accomplishes this by allowing simple drag and drop interface for configuration of the mappings and the integration rules. It’s event-action based orchestration engine automatically updates the relevant artifacts in both the systems keeping them in sync.

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.

QC to TFS and MTM-Scenario3

Omnibus Solution:

This requires migration of the core artifacts like Requirements, Test Cases and Bugs from QC to TFS along with the QTP Test Scripts associated with QC Test Cases. This is also supported in Kovair Omnibus and the QTP Test Scripts and the associated Test Cases can be migrated to TFS as Generic Tests. These automated Tests can be executed from MTM directly using QTP.

 

To understand how this migration from HP QC/HP ALM 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 for any questions.

Sign up for Demo
Software Training Program