TargetProcess CSV file Migration

Configuration file example

Create the JSON file with content like:

{
  "type": "targetprocess-csv",
  "debug": true,
  "oneByOne": false,
  "allureConfig": {
    "endpoint": "https://demo.testops.cloud/",
    "token": "73c54dba-4a77-4a2a-b8eb-b1aa5454ed90",
    "sslTrustAll": true,
    "projectId": 7,
    "migrationTagPrefix": "targetprocess",
    "folderCfPrefix": "Folder",
    "createOwner": true
  },
  "filesConfig": {
    "path": "/Users/user/path/New.List.1.csv"
  },
  "targetProcessCsvConfig": {
    "projectIds": [220752],
    "withTargetProcessIdCf": true,
    "withDefaultOwner": "accountName",
    "customFields": {
      "Project/Product": "Project/Product",
      "TestStructure": "TestStructure"
    }
  }
}

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:/path/to/file/TestCases.xml or /path/to/file/exampletest.xml
targetProcessCsvConfig.projectIds	no	If you want to migrate part of the cases to a specific TestOps project, use this property	[123, 432, 543]
targetProcessCsvConfig.withTargetProcessIdCf	no	If you want to have a custom field in TestOps with TargetProcessId, use this flag	username
targetProcessCsvConfig.withDefaultOwner	no	If you want to set a default owner for test cases in TestOps, make sure that the user with the specified username exists	false
targetProcessCsvConfig.customFields	no	A list of fields that need to be migrated to Allure as custom fields. Structure: "csv_header": "Allure_custom_field_name"	{"Project/Product": "Project/Product", "TestStructure": "TestStructure"}