Versions Compared

Old Version 2

changes.mady.by.user Sergio Freire

Saved on

compared with

New Version 3

changes.mady.by.user Sergio Freire

Saved on

Key

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

...

Supported FeaturesUnsupported
  • import Test case specification from HP ALM's "Test Plan"
    • tests without parameters
    • tests without called steps
    • tests that are not marked as "templates"
    • tests of type "MANUAL"
  • import Test attachments and Test step-level attachments
  • import formatted Test description
  • hierarchical organization information from ALM/QC's "Test Plan"
  • tests whose type is not "MANUAL"
  • tests with parameters
  • tests with called steps
  • tests that marked as being "templates"
  • defects and requirements
  • links to defects/requirements
  • hierarchical organization information
  • test runs
  • Test Lab-related information (tests, runs, etc.)

...

Info
titlePlease note

When you click Next, the connection is validated. If the connection fails, an error message is shown and you won't be able to proceed with the importation process.


Upon a successful connection, you will be promped with prompted to provide some additional configuration fields that allow you to fine tune the process.

...

Configuration options:

  • Label: an a unique label to add to the Test issues that will be created , so that they these can be quickly found afterwards
  • Hierarchical Test Organization: migrate  migrate hierarchical information from HP ALM/QC's "Test Plan" to Xray's Test Repository. Folders will be created, if needed, in the Test Repository and Tests will be moved to those the folders. 
  • Test Repository Path: the base Test Repository folder where ALM/QC's "Test Plan" hierarchical structured will be copied into. If "All" is selected, then the structure will be created in root of the Test Repository
  • HP QC Folder: the base folder where to import Tests from. Only the specified ALM/QC's "Test Plan" folder and its subfolders, along with respective Test cases, will be imported. Folder path must be specified in the format "Parent Folder/Child Folder"; leave it empty to import all folders

...

We recommend using a unique label with numbers  to numbers to assign the Test issues that will be created. This may be quite useful if you need a quick way to identify the newly created issues. The label syntax is restricted in the same way as label fields in Jira.

...