HP ALM migration

WARNING

MIGRATION AVAILABLE FOR ALLURE TESTOPS VERSION > 4.26.0

Configuration file example

Create the json file with content like:

{
  "type": "alm",
  "debug": true,
  "requestLog": true,
  "allureConfig": {
    "endpoint": "https://demo.testops.cloud/",
    "token": "bf012aac-f2ca-4bdd-a30c-9f427901e239",
    "sslTrustAll": true,
    "projectId": 29,
    "migrationTagPrefix": "alm",
    "folderCfPrefix": "Section"
  },
  "almConfig": {
    "endpoint": "http://example.com:8080",
    "username": "admin",
    "password": "admin",
    "domainName": "DEFAULT",
    "projectName": "Test1",
		"ownerFieldName": "some-alm-field-name",
    "customFields": {
      "subtype-id": "Type",
      "alm test field name": "Allure cf name"
    }
  }
}

Configuration parameters

Name	Mandatory	Description	Example
commonProperties	yes	see description here: Common properties
allureConfig	yes	see description here: Allure TestOps properties
almConfig.endpoint	yes	ALM instance url
almConfig.username	yes	ALM username
almConfig.password	yes	ALM password
almConfig.domainName	yes	ALM domain name	DEFAULT
almConfig.projectName	yes	ALM project name	test1
almConfig.ownerFieldName	no	Use it to map the value from field into TestOps Member owner	owner
almConfig.customFields	no	A list of cf values which need to be migrate to allure as custom fields. To map fields from alm test you should specify the name "customFields": { "subtype-id": "Type" }