Appearance
Allure TestOps properties
Allure TestOps Configuration file example
json
"allureConfig": {
"endpoint": "https://demo.testops.cloud/",
"token": "allure-testops-token",
"sslTrustAll": true,
"projectId": 6,
"migrationTagPrefix": "testrail",
"folderCfPrefix": "Section",
"stepNamePrefix": "Step",
"issueTrackerId": 3,
"workflowId": -1
},
Configuration parameters
Name | Mandatory | Description | Example |
---|---|---|---|
allureConfig.endpoint | yes | Allure TestOps instance url | |
allureConfig.token | yes | Allure TestOps token (please use the token from user with admin rights) | |
allureConfig.sslTrustAll | no | Set to true if self-signed certificates are used and you trust them. | true |
allureConfig.projectId | yes | Existing Allure TestOps project id to migrate test cases to. | 12 |
allureConfig.migrationTagPrefix | no | An indicator for the migration test. Will be used as a tag to identify the migrated testcase. The "migration" keyword will be used if nothing specified. | testrail |
allureConfig.folderCfPrefix | no | The name for sections custom field. On the Allure TestOps the custom fields will be created: Section1, Section2, Section3, etc. | Section |
allureConfig.stepNamePrefix | no | Prefix for steps if no name exist Will be like Step 0 Step 1 Step 2 … | Step |
allureConfig.issueTrackerId | no | If the test cases contain attributes, that are mapping test cases to available, the issues there can be mapped into the issuetracker specified in the Allure TestOps. | 3 |
allureConfig.createOwner | no | If you want tho create a read only users during migration for owners set this option to true. Default (false) | true |
allureConfig.allowedUsernameAsEmail | no | If it is allowed to have an username as emain in your TestOps system | |
allureConfig.workflowId | no | If you want to migrate with custom workflow use this propert | 3 |
allureConfig.stepsWithExpectedResult | no | If your TestOps version (> 4.22.1) support expected results in steps. https://qameta.io/blog/testops-for-manual-testers/ | true |
allureConfig.newCfApi | no | If your TestOps version (≥ 4.25.1) set it to true | true |