Zephyr HP ALM Migration Adapter Overview

Owned by Helen Kosova (Deactivated)
Aug 31, 2020

Table of Contents

Introduction

Zephyr HP ALM Migration Adapter is a unique API-driven solution that lets you migrate your data from HP ALM directly into Zephyr Enterprise. The solution works with either an On-Prem or a Cloud installation of Zephyr Enterprise.

  • Please see below for compatible versions the HP ALM tool.
  • Users can retrieve the HP ALM Migration Adapter from the following download page (utility name 'HPQC-ZS-<release>')


Version History

VersionRelease DateRelease Notes
0.1

September 08, 2017

Initial version.
1.0

May 23, 2018

Added support for additional entities.
1.1
July 25, 2019
Added support for self-signed certificates.
1.2
September 16, 2019

Improved migration of test cases to a specific Releases instead of at the Project level.

Bug fixes.

1.3

October 30, 2019

  • Test cases have been moved to the project level.
  • Test cases can now be added to releases as cycles and phases.
  • Now you can map a requirement to a test case if it is mapped in HP ALM:
    • Test cases which do not belong to a test set will be moved to the default release of Zephyr Enterprise along with mapped requirements to maintain mapping coverage.
1.4

June 18, 2020

A number of bugs reported by our customers have been fixed.

1.4.1July 16, 2020A number of bugs reported by our customers have been fixed.
1.5

June 18, 2020

Compatibility with Zephyr Enterprise 6.7.x.

1.5.1July 16, 2020A number of bugs reported by our customers have been fixed.

ALM and Zephyr Compatibility


ALM Adapter VersionZE VersionHP ALM/QC Version
0.1 6.1 - 6.611.52 and 12.55
1.06.1 - 6.611.52 and 12.55
1.16.1 - 6.611.52 and 12.55
1.26.1 - 6.611.52 and 12.55
1.36.1 - 6.6

11.52 and 12.55

1.46.1 - 6.6

11.52 and 12.55

1.56.7 and above

11.52 and 12.55

Planning

Planning is an important phase of migration. This phase involves:

  1. Determining HP ALM artifacts that need to be migrated

  2. Reviewing environments and configurations

  3. Optimizing stage environments

The sections below explain these in more details:

  • Determine HP ALM artifacts that need to be migrated

    It is important to acknowledge that not all the data you have in legacy system remains good to be transferred. In this phase, you should review how your testing methodologies and practices have changed over time and determine the right HP ALM artifacts that makes sense to transfer to Zephyr.


  • Review environments and configurations

    Not all HP ALM environments are configured the same. Please review the hardware configuration, memory allocation, API throttling configurations, network topology etc for each HP ALM environment.


  • Determine the migration style

    There are two possibilities for the migration: big bang migration or trickle migration.

    In big bang migration, the process is conducted over a weekend when both HP ALM and Zephyr are shut down for users. With this approach, we suggest at least one dry run of the migration in a stage environment before the live event.

    In trickle migration, you may take an incremental approach by having both HP ALM and Zephyr available in parallel during weeks/months, and moving projects from HP ALM to Zephyr based on business needs.

    With either approach, we undertake at least one week of review, preparation and optimization of stage environment; this includes optimization of system that has Zephyr HP ALM Migration adapter installed. Full access to stage environment is required.


Adapter Overview

The Zephyr HP ALM Migration adapter uses REST APIs to extract data from HP ALM and import data into Zephyr Enterprise. The section below provides a high-level overview of the communication between the Zephyr Enterprise instance, the HP ALM instance, and the Zephyr HP ALM Migration adapter:


Supported Migration Entities

The current version of the Zephyr HP ALM Migration Adapter supports migration of the following types of entities:

  • Projects
  • Users
  • Requirements
  • Tests
  • Test Attachments
  • Test Steps
  • Step Attachments
  • Test Folder Organization
  • Test Custom Fields
  • Release
  • Cycle
  • Test Run (Test Execution in Zephyr)


Migrating Defects from HP ALM to Jira

The current process for migrating historical defects from HP ALM into JIRA involves the following steps:

  • The defects are exported from HP ALM using APIs available from HP
  • The defects are then imported into JIRA by using JIRA REST API calls or via a .CSV file


Setup & Usage Instructions

For setup and usage instructions, please refer to Using the Zephyr HP ALM Migration Adapter.


Additional Questions

For any questions, please contact Zephyr Support: https://support.getzephyr.com