TestLink XML file Migration

WARNING

MIGRATION AVAILABLE FOR ALLURE TESTOPS VERSION > 4.26.0

Configuration file example

Create the JSON file with content like:

{
  "type": "testlink-xml",
  "debug": true,
  "oneByOne": false,
  "allureConfig": {
    "endpoint": "https://demo.testops.cloud/",
    "token": "1f4b4acd-418c-4d0b-8533-1d747abb7599",
    "projectId": 9999,
    "migrationTagPrefix": "testlink",
    "folderCfPrefix": "Folder"
  },
  "filesConfig": {
    "path": "c:/path/to/file/exampletest.xml"
  },
  "testLinkXmlConfig": {
		"customFields": {
      "execution_type": "Type",
      "keyword": "Keyword",
      "custom_somecustom_field_name": "Allyre CF name"
      "test link system field name": "Allure TO cf name"
    },
		"statusMapping": {
      "5": "Outdated",
      "7": "Active",
      "1": "Draft",
      "2": "Review"
    },
    "customFieldsMapping": [
      {
        "name": "execution_type",
        "values": {
          "1": "Manual",
          "2": "Auto"
        }
      },
      {
        "name": "TestLink customfieldname",
        "values": {
          "1": "Allure TO customfieldvalue 1",
          "2": "Allure TO customfieldvalue 2",
        
        }
      }
    ]
  }
}

Configuration parameters

Name	Mandatory	Description	Example
commonProperties	yes	see description here: Common properties
allureConfig	yes	see description here: Allure TestOps properties
filesConfig.path	yes	Absolute path to XML file with TestLink export	C:/Dev/Tools/TestCases.xml or /path/to/file/exampletest
testLinkXmlConfig.customFields	no	A list of TestLink fields which need to be migrated to Allure as custom fields. Structure: "testlink_field_name": "Allure_custom_field_name" If the value is represented as an ID in the TestLink XML file, values mapping can be specified in the customFieldsMapping field. For system fields like execution_type, no prefix is needed. For custom fields from custom_fields tag, use the prefix custom_. Example: custom_Платформа, custom_some_name	{ "suite_id": "Suite", "priority_id": "Priority", "custom_tester": "Owner", "custom_system": "System" }
testLinkXmlConfig.statusMapping	no	The mapping for statuses. The default mapping is shown in the example. If you want to use it, don’t add this config into the file. All other different statuses will be mapped to “Draft” if no other rule is specified.	{ "5": "Outdated", "7": "Active", "1": "Draft", "2": "Review" }
testLinkXmlConfig.customFieldsMapping	no	A TestLink ID-to-value mapping. Structure: - name: TestLink field name - values: A map with ID and its value.	[ { "name": "execution_type", "values": { "1": "Low", "2": "Medium", "3": "High", "4": "Critical" } }, { "name": "system_field_name", "values": { "1": "Tester QA1", "2": "Tester QA2", "3": "Tester QA3", "4": "Tester QA4" } } ]