ContributionsMost RecentMost LikesSolutionsRe: Unable to Publish Cucumber Tests Results, using Jenkins (pluggin zephyr scale), to Zephyr Scale ykowalko That api endpoint should be available on Zephyr Scale Server. I'm not entirely sure that is what the Jenkins plugin uses (though that would make sense). But it's the endpoint that we use to test uploads manually with Postman. I was able to upload your tests to our instance by saving the text as a .json file and zipping (zipfile attached). Perhaps the issue is that the file extension on your file is ".xml". If the file extension is not ".json" in Postman, the error "Invalid zip file" is returned. Maybe that is the error that Jenkins is reporting. Note the tags arrays were removed from the json in the attached zip file since otherwise there's an error about no matching test key. Re: Zephyr Postman Post API Request delivers Internal Error on v2/automations/executions/cucumber Amrit13 , can you please post the content of your cucumber json report? If you are using wdio-cucumberjs-json-reporter, the issue could be output like the below in the json report, which records an "element" the feature corresponding to the feature itself (keyword: Scenario, type: feature), and has an empty steps: [] array. The Zephyr scale https://usjira.iscinternal.com/rest/atm/1.0/automation/execution/cucumber api doesn't support empty steps arrays. The latest wdio-cucumber-js-json reporter has been fixed so you can download the latest version 4.1.4 and try again (https://github.com/webdriverio-community/wdio-cucumberjs-json-reporter/issues/68) "tags": [], "elements": [ { "keyword": "Scenario", "type": "feature", "description": "", "name": "PAYS - Russia - telecommandes header-main-menu - CTA", "tags": [], "id": "pays---russia---telecommandes-header-main-menu---cta;pays---russia---telecommandes-header-main-menu---cta", "steps": [] }, Re: Unable to Publish Cucumber Tests Results, using Jenkins (pluggin zephyr scale), to Zephyr Scale ykowalko the issue is this output in the json report, which records an "element" the feature corresponding to the feature itself (keyword: Scenario, type: feature), and has an empty steps: [] array. The Zephyr scale https://usjira.iscinternal.com/rest/atm/1.0/automation/execution/cucumber api (which I presume the Jenkins plugin uses) doesn't support empty steps arrays. The latest wdio-cucumber-js-json reporter has been fixed so you can download the latest version 4.1.4 and try again (https://github.com/webdriverio-community/wdio-cucumberjs-json-reporter/issues/68) "tags": [], "elements": [ { "keyword": "Scenario", "type": "feature", "description": "", "name": "PAYS - Russia - telecommandes header-main-menu - CTA", "tags": [], "id": "pays---russia---telecommandes-header-main-menu---cta;pays---russia---telecommandes-header-main-menu---cta", "steps": [] }, You can also test the uploads separately via url --basic --user ****:******** -F "file=@login.zip" https://usjira.iscinternal.com/rest/atm/1.0/automation/execution/cucumber/DP?autoCreateTestCases=true Can any customers running large numbers of automated tests comment on any Jira performance impact? Can anyone who uploads a large volume of automated test results to Zephyr scale comment on scalability, e.g., whether there has been any performance impact observed on the Jira instance? Is there a need to archive old test executions?