Support team answered me that there is no junit impor funcionality in server version, but only in cloud version.
i implemented by myself parsing the xml and using server api to create-update test results.
i'm using the server documentation,
maybe the problem can be with the endpoint?
following documentation https://support.smartbear.com/zephyr-scale-server/api-docs/v1/ it should to be something like
http://your-jira-host:port/your-jira-context/rest/atm/1.0/
but taking a look at the network in chrome i found a call with this endpoint
and the api works using /rest/tests/1.0/testcase/search but not using /rest/atm/1.0/ as described
but if i point to
https://jira.namirial.com/rest/tests/1.0/automation/execution/CUSTOMPRJ
i obtain
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<status>
<status-code>404</status-code>
<message>null for uri: https://jira.namirial.com/rest/tests/1.0/automation/execution/CUSTOMPRJ</message>
</status>
instead if i point to https://jira.namirial.com/rest/atm/1.0/automation/execution/CUSTOMPRJ
the endpoint is recognized but the api respond that there are a invalid custom format json file
i tried with
As a test, you could use another rest/atm endpoint to make sure it's working for you. This endpoint works for me:
https://jira.[YOUR INSTANCE].com/rest/atm/1.0/testrun/[YOUR TEST CYCLE]/testresults
If that's working for you, and the JSON file you're providing is in the correct format as mentioned in the documentation here (smartbeartm4j / tm4j-junit-integration — Bitbucket) then I'm sorry I can't help. I've only used the APIs for GET functions and not very often.
i make other tests and i understand that the api doesn't want a junit.xml file but a json file formatted as zephyr wants, as for example
{
"version": 1,
"executions":[
{
"source":"CalculatorSumTest.sumTwoNumbersAndPass",
"result":"Passed",
"testCase": {
"key": "QA-T1"
}
},
{
"source":"CalculatorSumTest.sumTwoNumbersAndFail",
"result":"Failed",
"testCase": {
"key": "QA-T2"
}
},
{
"source":"CalculatorSumTest.notMappedToTestCaseAndPass",
"result":"Passed"
},
{
"source":"CalculatorSumTest.mappedToTestCaseNameAndPass",
"result":"Passed",
"testCase": {
"name": "Mapped to Test Case Name and Pass"
}
}
]
}as described here https://bitbucket.org/smartbeartm4j/tm4j-junit-integration/src/master/
but here https://support.smartbear.com/zephyr-scale-cloud/docs/test-automation/pytest-integration.html documentation talk about uploading a simple xml file, not a json file, but using this api https://support.smartbear.com/zephyr-scale-cloud/api-docs/#operation/createJUnitExecutions that doesn't exists for the server version.
Can Zephyr Server version be updated to accept the createJUnitExecutions api?
Sorry but I can only suggest raising a request with the SmartBear support team at this link: Login - Jira Service Management (atlassian.net)
But josh42 might also be able to help?
Hi guys,
I work with the server API quite extensively, but have not used the JUnit integration, yet. I can only refer you to the docs
https://support.smartbear.com/zephyr-scale-server/docs/test-automation/integrations/junit.html
One thing, I can clear up is the difference between the API endpoints using rest/atm/... and the ones using rest/tests/...
The atm ones are the public API endpoints of Zephyr Scale which are documented for public use.
The tests endpoints are the internal ones that ZS uses. So those are not meant for public use and thus are not documented publicly. They can be quite handy, if you are savvy enough to figure them out (because they return a lot more information - like internal ids and such - than the public endpoints) but you will always run the risk of running into undocumented changes in the API and not getting the same sort of support than you get for the official API (also, you can break stuff quite easily using these endpoints, so be careful).
As for the rest, I'm with MisterB , raise a feature request for the server API and in the meantime contact support directly to have them help you figure out, why your JUnit results do not have the right format.
Cheers
Josh
