Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Base URL: Zephyr Enterprise URL in the format: <URL>

  • Username: Zephyr Enterprise Username and Password

...

Step 2: QMetry Login

...

You can map the values of your different fields of Zephyr Enterprise to that of QMetry.

Migration Tool provides an option of "Add value" if user wants to create a new field value in QMetry same as Zephyr offers. To create the new values > Click on the checkbox beside the field value > Click on "Add value" button below > Now map the Zephyr field values to the newly created QMetry fields values.

NOTE: The Add Value option is not available for test execution values and test step execution values.

Field Value Mapping for Requirements 

...

Once the migration completes, you can log in to QMetry and verify all the migrated data in your given projects.

Post-requisite

The migration utility is designed to support resuming the data migration from the same point in case an error is encountered due to data issues or other reasons. In such cases re-migrating the project is not necessary. At times when you run into errors, you can try to resume the migration after capturing the logs as follows.

  1. Capture Migration Logs

    • The logs should be present in the logs folder of the migration utility directory containing the .war file. Zip the logs folder and send it to QMetry Support for investigation.

  2. Resume the Migration

    • The migration can be resumed by refreshing the existing page and clicking "Resume" OR from the URL : http://<utility_url>/migrate2qtm/migration

  3. Reverting API metering, Audit history logging and Email Notifications.

    • Once the projects have been migrated, or in cases when users would use QMetry and no projects would be migrated for significant amount of time, in those cases these changes should be reverted.

    • Refer to the Pre-requisite for the changes required.

...

  • For test cases, Created Date will be migrated to QMetry's system field and for other entities created date will be migrated as custom field, if user wants.

  • ALT Id will be migrated as externalID.

  • Test Planning (containing phases and folders) is migrated as test suites to QMetry

  • Zephyr's ‘checkbox’ type Custom field will be migrated as a string (e.g. if checkbox is checked, then the value in the field will be displayed "True" in QMetry).

  • If a duplicate folder is found in the same level of hierarchy, then that folder will be migrated with ID appended to the folder name.

  • Folders are created according to the Zephyr Enterprise Releases. Zephyr Enterprise assets are then migrated in these folders.

  • If Testcases are shared(i.e. Testcase has same ID) amongst multiple Releases in Zephyr, then new Testcases(i.e. each Testcase with a unique ID) will be created for respective Releases in QMetry.

  • Migration Tool will not migrate execution of a deleted Testcase.

  • If a duplicate Release is found, then that Release will be migrated with ID appended to the release name.

  • Migration Tool does not migrate Hidden Releases and its Assets.

Limitations

  • Zephyr Enterprise users are not migrated to QMetry.

  • Dashboards, Graphs, History logs are not migrated.

  • Attachments: Attachment files exceeding 100 MB are not migrated.

  • Test Case/Test Execution where Assigned to="Anyone", it will get assigned to admin.

...