...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Redirect | ||||||
|---|---|---|---|---|---|---|
|
Table of Contents
...
| 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 Standalone. The solution works with either an On-Prem or a Cloud installation of Zephyr Standalone.
| Note |
|---|
The HP ALM Migration works with HP ALM 11.5 and above. Users can retrieve the HP ALM Migration Adapter from the following download page (utility name 'HPQC-ZS-<release>') |
Version History
| Version | Release Date | Release Notes |
|---|---|---|
| 0.1 | Initial version | |
| 1.0 | Added support for additional entities | |
| 1.1 | Added support for self-signed certificates | |
| 1.2 | Improved migration of test cases to a specific Releases instead of at the Project level Bug fixes |
Planning
Planning is an important phase of migration. This phase involves:
Determining HP ALM artifacts that need to be migrated
Reviewing environments and configurations
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 Standalone. The section below provides a high-level overview of the communication between the Zephyr Standalone 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.