TestIT migration

WARNING

MIGRATION AVAILABLE FOR ALLURE TESTOPS VERSION > 4.26.0

Configuration file example

Create the json file with content like:

{
  "type": "testit",
  "debug": true,
  "requestLog": false,
  "oneByOne": true,
  "allureConfig": {
    "endpoint": "https://demo.testops.cloud/",
    "token": "api-token",
    "sslTrustAll": true,
    "projectId": 114,
    "migrationTagPrefix": "testit",
    "folderCfPrefix": "Section"
  },
  "testItConfig": {
    "endpoint": "https://demo.testit.software/",
    "token": "api-token",
    "sslTrustAll": true,
    "projectId": 45,
    "testCaseIds": [1,2,3],
    "epFeStSections": true,
    "prePostStepsWithoutExpected": false,
    "customFields": {
      "priority": "Priority",
      "test it atribute name": "Allure cf name"
    },
		"statusMapping": {
      "NotReady": "Outdated",
      "Ready":"Active",
      "NeedsWork": "Draft"
    }
  }
}

Configuration parameters

Name	Mandatory	Description	Example
commonProperties	yes	see description here: Common properties
allureConfig	yes	see description here: Allure TestOps properties
testItConfig.endpoint	yes	TestIt instance url
testItConfig.token		TestIt token
testItConfig.sslTrustAll	no	Flag if the host validation should take place. Example "true".	true
testItConfig.projectId	yes	testit 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]
testitConfig.epFeStSections	no	Epic Feature Story Schema For Sections: For Section1, a custom field value for Epic will be added in Allure For Section2, a custom field value for Feature will be added in Allure For Section3, a custom field value for Story will be added in Allure	false
testitConfig.prePostStepsWithoutExpected	no	Set true if you need steps without expected, only actions	false
testitConfig.withoutTags	no	Set to true if you don’t want to migrate tags from TestIt	false
testitConfig.preconditionStepsInScenario	no	Set it to true to migrate precondition steps into TestOps testcase scenario	false
testitConfig.preconditionStepsAsTable	no	If you want to migrate precondition steps as a table. It will be a list by default.	true
testitConfig.postconditionStepsInScenario	no	Set it to true to migrate postcondition steps into TestOps testcase scenario	false
testItConfig.customFields	no	A list of custom field values to migrate to Allure as custom fields. Only the priority system field is supported for now. To map an attribute from TestIt, specify only the attribute name (string, optional, multipleOptions types supported). "customFields": { "Suite": "Suite", "Feature": "Feature" }
testItConfig.statusMapping	no	The mapping for statuses. The default mapping is shown in the example. To use the default, do not add this config to the file. All other statuses will map to “Draft” if not specified otherwise. "statusMapping": { "NotReady": "Outdated", "Ready": "Active", "NeedsWork": "Draft" }
testItConf.issuesPattern	no	Specify the pattern to fetch issue keys from links. Ensure that allureConfig contains the property issueTrackerId. "issuesPattern": "https://jira.frrfg.com/browse/(?<id>[a-zA-Z0-9-]*)"
testItConf.attributesWithIssues	no	Specify the list of attribute names to convert to issue links. "attributesWithIssues": ["link1", "link2"]