Allure TestOps migration

WARNING

MIGRATION AVAILABLE FOR ALLURE TESTOPS VERSION > 4.26.0

Configuration file example

Create the json file with content like:

{
  "type": "testops",
  "debug": true,
  "requestLog": false,
  "oneByOne": true,
  "allureConfig": {
    "endpoint": "https://demo.testops.cloud/",
    "token": "api-token",
    "sslTrustAll": true,
    "projectId": 96,
    "migrationTagPrefix": "testops"
  },
  "testopsConfig": {
    "endpoint": "https://old-allure-testops-endpoint/",
    "token": "api-token",
    "sslTrustAll": true,
    "projectId": 3,
    "testCaseIds": [1,2,3],
    "customFields": {
      "Feature": "Feature",
      "Story": "Story"
    }
  }
}

Fields description

Name	Mandatory
commonProperties	yes	see description here: Common properties
allureConfig	yes	see description here: Allure TestOps properties
testopsConfig.endpoint	yes	Old Allure TestOps instance url
testopsConfig.token		Old Allure TestOps token
testopsConfig.sslTrustAll	no	Flag if the host validation should take place. Example "true".	true
testopsConfig.projectId	yes	Old testops project id	2
testItConfig.testCaseIds	no	A list of specific cases for migration can be specified. Without this parameter the migration will be done for all cases in the project	[1,2,3]
testopsConfig.customFields	no	A list of cf values which need to be migrate to allure as custom fields. "customFields": { "Suite": "Suite", "Feature": "Feature" }