External execution results from either automated and manual Tests can be imported to Jira. This operation may be done in one of two ways:

  • Manually, using the Import Execution Results action accessible from the Test Execution issue screen
  • via the REST API to integrate with Continuous Integration (CI) platforms or other external execution processes. Please refer to the Xray REST API.

When manually importing execution results, the current Test Execution issue will be updated with the results. When using the REST API, you can specify an existing Test Execution issue in Jira; if the Test Execution key is missing, Xray will create a new Test Execution issue based on the information provided.

Supported Import Formats

Xray supports the following formats for importing execution results:

  1. Cucumber JSON output format
  2. JUnit XML output format
  3. NUnit XML output format
  4. Xray JSON format

Cucumber JSON output format

The Cucumber tool is capable of generating multiple reports for an execution. In order to import the execution results to Xray, Cucumber must generate a JSON output (example here) using the following arguments:

-f, --format FORMAT       How to format features. Available formats compatible with Xray for JIRA:
             	json        : Prints the feature as JSON
                json_pretty : Prints the feature as prettified JSON
-x, --expand              Expand Scenario Outline Tables in output.
 
Ex:
> cucumber -x -f json

JUnit XML output format

Xray supports a JUnit XML format for importing execution results.

<?xml version="1.0" encoding="UTF-8"?>
<testsuite tests="1" failures="0" name="ut.com.xpandit.raven.service.impl.IssueDataSetTest" time="0.114" errors="0" skipped="0">
  <properties>
    ...
  </properties>
  <testcase classname="ut.com.xpandit.raven.service.impl.IssueDataSetTest" name="testApplyOptions_withValidIssueAndValidLimitOverflowOption_returnsExpectedSubset" time="0.114"/>
</testsuite>

Xray-JUnit XML extension format

Users are also able to import JUnit results using the Xray extended format.

This format adds the following property elements:

  • testrun_comment
  • requirements
  • test_key
  • test_id
  • test_description
  • test_summary
  • tags
  • testrun_customfields
  • testrun_evidence

For more detailed information, visit the Xray App GitHub repository: https://github.com/Xray-App/xray-junit-extensions.

NUnit v3.0 XML output format

Xray supports an NUnit v3.0 XML format for importing execution results.

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<test-run id="0" testcasecount="3" total="3" passed="3" failed="0" inconclusive="0" skipped="0" asserts="3" result="Passed" portable-engine-version="3.3.0.0" start-time="2016-12-26 14:36:03Z" end-time="2016-12-26 14:36:03Z" duration="0.015218">
  <test-suite type="Assembly" id="1021" name="x, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" fullname="x, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" runstate="Runnable" testcasecount="14" result="Failed" site="Child" start-time="2016-12-26 14:36:03Z" end-time="2016-12-26 14:36:03Z" duration="0.015218" total="3" passed="3" failed="0" inconclusive="0" skipped="0" asserts="3">
    <settings>
      ...
    </settings>
    <test-suite type="TestSuite" id="1022" name="x" fullname="x" runstate="Runnable" testcasecount="12" result="Passed" start-time="2016-12-26 14:36:03Z" end-time="2016-12-26 14:36:03Z" duration="0.015218" total="3" passed="3" failed="0" inconclusive="0" skipped="0" asserts="3">
    <test-suite type="TestFixture" id="1004" name="CalculatorTests" fullname="x.CalculatorTests" classname="x.CalculatorTests" runstate="Runnable" testcasecount="12" result="Passed" start-time="2016-12-26 14:36:03Z" end-time="2016-12-26 14:36:03Z" duration="0.014979" total="3" passed="3" failed="0" inconclusive="0" skipped="0" asserts="3">
      <test-suite type="ParameterizedMethod" id="1008" name="CanAddNumbers" fullname="x.CalculatorTests.CanAddNumbers" classname="x.CalculatorTests" runstate="Runnable" testcasecount="3" result="Passed" start-time="2016-12-26 14:36:03Z" end-time="2016-12-26 14:36:03Z" duration="0.004228" total="3" passed="3" failed="0" inconclusive="0" skipped="0" asserts="3">
        <properties>
              <property name="Requirement" value="DEV-771" />
            </properties>
    <test-case id="1005" name="CanAddNumbers(1,1,2)" fullname="x.CalculatorTests.CanAddNumbers(1,1,2)" methodname="CanAddNumbers" classname="x.CalculatorTests" runstate="Runnable" seed="1846389584" result="Passed" start-time="2016-12-26 14:36:03Z" end-time="2016-12-26 14:36:03Z" duration="0.001194" asserts="1" />
    <test-case id="1006" name="CanAddNumbers(-1,-1,-2)" fullname="x.CalculatorTests.CanAddNumbers(-1,-1,-2)" methodname="CanAddNumbers" classname="x.CalculatorTests" runstate="Runnable" seed="1113780989" result="Passed" start-time="2016-12-26 14:36:03Z" end-time="2016-12-26 14:36:03Z" duration="0.000067" asserts="1" />
    <test-case id="1007" name="CanAddNumbers(100,5,105)" fullname="x.CalculatorTests.CanAddNumbers(100,5,105)" methodname="CanAddNumbers" classname="x.CalculatorTests" runstate="Runnable" seed="1585332966" result="Passed" start-time="2016-12-26 14:36:03Z" end-time="2016-12-26 14:36:03Z" duration="0.000103" asserts="1" />
    </test-suite>
  </test-suite>
  </test-suite>
</test-suite>
</test-run>

NUnit v2.6 XML output format

Xray supports an NUnit v2.6 XML format for importing execution results.

<?xml version="1.0" encoding="utf-8" standalone="no"?>
<test-results name="MobilityServices.ShoppingLists.Tests\bin\Debug\MobilityServices.ShoppingLists.Tests.dll" total="2" errors="0" failures="0" not-run="0" inconclusive="0" ignored="0" skipped="0" invalid="0" date="2017-01-18" time="15:46:53">
  <environment nunit-version="2.6.4.14350" clr-version="2.0.50727.8745" os-version="Microsoft Windows NT 6.2.9200.0" platform="Win32NT" cwd="D:\Work\Apps\NUnit-2.6.4\bin" machine-name="LAPTOP-UNKNOWN" user="unknown" user-domain="LAPTOP-UNKNOWN" />
  <culture-info current-culture="pt-PT" current-uiculture="en-GB" />
  <test-suite type="Assembly" name="MobilityServices.ShoppingLists.Tests\bin\Debug\MobilityServices.ShoppingLists.Tests.dll" executed="True" result="Success" success="True" time="4.473" asserts="0">
    <results>
      <test-suite type="Namespace" name="MobilityServices" executed="True" result="Success" success="True" time="4.473" asserts="0">
        <results>
          <test-suite type="Namespace" name="ShoppingLists" executed="True" result="Success" success="True" time="4.473" asserts="0">
            <results>
              <test-suite type="Namespace" name="Tests" executed="True" result="Success" success="True" time="4.473" asserts="0">
                <results>
                  <test-suite type="Namespace" name="Controllers" executed="True" result="Success" success="True" time="4.473" asserts="0">
                    <results>
                      <test-suite type="TestFixture" name="ShoppingListsControllerTests" executed="True" result="Success" success="True" time="4.473" asserts="0">
                        <results>
                          <test-case name="JMMobilityServices.ShoppingLists.Tests.Controllers.ShoppingListsControllerTests.RemoveShoppingListItem" executed="True" result="Success" success="True" time="4.118" asserts="2" />
                          <test-case name="JMMobilityServices.ShoppingLists.Tests.Controllers.ShoppingListsControllerTests.TestAuthorization" executed="True" result="Success" success="True" time="0.355" asserts="1">
                            <properties>
                              <property name="Requirement" value="DEV-771" />
                            </properties>
                          </test-case>
                        </results>
                      </test-suite>
                    </results>
                  </test-suite>
                </results>
              </test-suite>
            </results>
          </test-suite>
        </results>
      </test-suite>
    </results>
  </test-suite>
</test-results>

Xray JSON format

Xray also provides a proprietary JSON format for importing execution results.

Although Xray supports multiple report formats used by different testing frameworks/runners (e.g. JUnit, NUnit, xUnit, TestNG, Cucumber, Robot Framework), there are scenarios where using these formats is not an option like:

  • Importing results for manual Tests;
  • Using a testing framework report that is not supported by Xray;
  • Having your own testing framework;
  • Limited support of existing formats to import detailed execution results back into Jira.


Importing Execution Evidence

This format supports importing execution evidence (attachments) embedded in the JSON file encoded in Base 64.

Creating new Test Execution issues

The info object allows you to specify specific execution information when creating new Test Execution issues.

Importing results to Manual Tests

You can import manual Test execution results using the steps element for specifying the Test step results.



testExecutionKeyThe test execution key where to import the execution results
infoThe info object for creating new Test Execution issues (link)
testsThe Test Run result details (link)

addTestsToPlan

Whether the tests must be added to the Test Plan as well can impact the performance. (link)

"info" object - Test Execution issue

You can specify which Test Execution issue to import the results by setting the test execution key on the testExecutionKey property. Alternatively, you can create a new Test Execution issue for the execution results and specify the issue fields within the info object.

projectThe project key where the test execution will be created
summaryThe summary for the test execution issue
descriptionThe description for the test execution issue
versionThe version name for the Fix Version field of the test execution issue
revisionA revision for the revision custom field
userThe username for the Jira user who executed the tests
startDateThe start date for the test execution issue
finishDateThe finish date for the test execution issue
testPlanKeyThe test plan key for associating the test execution issue
testEnvironmentsThe test environments for the test execution issue

"tests" object - Test Run details

The test run details object allows you to import any detail about the execution itself. All Xray test types are supported. 

It is possible to import a single result (the test object itself with the "steps" (Manual tests) or "examples" (BDD tests)) or multiple execution results into the same Test Run (data-driven testing) using the "iterations" array.

If you have Xray Enterprise installed, if the "testVersion" is provided Xray will import the results using the provided test version as the base for the Test Run. Otherwise, Xray will try to resolve the imported execution result into an active test version. The Default version will be chosen if determined to be of the same Test Type. If not, Xray will use the latest active test version if the same Test Type.

testKeyThe test issue key
testInfoThe testInfo element (link)
testVersionThe Test Version to import the result
startThe start date for the test run
finishThe finish date for the test run
commentThe comment for the test run
executedByThe user id who executed the test run
assigneeThe user id for the assignee of the test run
statusThe test run status (PASS, FAIL, EXECUTING, TODO, custom statuses ...)
stepsThe step results (link)
examplesThe example results for BDD tests (link)
iterationsThe iteration containing data-driven test results (link)
defectsAn array of defect issue keys to associate with the test run
evidenceAn array of evidence items of the test run (link)
customFieldsAn array of custom fields for the test run (link)

"testInfo" object - Creating Test issues

It is possible to create new test issues when importing execution results using the Xray JSON format. For this, a testInfo element must be provided in order for Xray to create the issues.

If it is the first time you are importing an execution with a testInfo, Xray will create the tests automatically. Subsequent executions will reuse the same test issues.

Xray will first try to match test issues by the testKey if present. Otherwise, Manual or BDD tests are matched by summary whilst Generic tests are matched using the generic definition field, within the same project.

If Xray Enterprise is installed, and if the Test issue is identified by testKey or summary, and if the Test Type of the testInfo element does not exist in any version of the Test, then a new version will be created automatically for the new definition. Otherwise, Xray will update the existing Test version using the default if the Test Type matches or the latest active version of the same Test Type. 

Any changes to the testInfo element will update the test issue specification in Jira.
If the match field (summary or definition) is changed, Xray will search for another issue and will create a new test case, or update an existing test case if no one is found. If you need to change the summary or the definition, you can do it manually (go to Jira and change the field), or you can include the testKey within the test element.

projectKeyThe project key where the test issue will be created
summaryThe summary for the test issue
descriptionThe description of the test issue
testTypeThe test type (e.g. Manual, Cucumber, Generic)
requirementKeysAn array of requirement issue keys to associate with the test
labelsThe test issue labels
stepsAn array of test steps (for Manual tests) (link)
definitionThe generic test definition
scenarioThe BDD scenario
scenarioTypeThe BDD scenario type (Scenario or Scenario Outline)

"steps" object - step definition

This object allows you to define the step fields for manual tests.

actionThe step action - native field
dataThe step data - native field
resultThe step expected result - native field

"iterations" object - Data-driven test results

If you need to import data-driven test results you need to use the iterations object. Xray will store all iterations within the same Test Run object. 

It is also possible to import iteration results with parameters. Currently, this is only supported for manual tests.

In this case, Xray will create a dataset automatically within the Test Run object.

nameThe iteration name
parametersAn array of parameters along with their values (link)
statusThe status for the iteration (PASS, FAIL, EXECUTING, TODO, custom statuses ...)

"parameters" object - parameters within iteration results

nameThe parameter name
valueThe parameter value

"evidence" object - embedded attachments

dataThe attachment data encoded in base64
filenameThe file name for the attachment
contentTypeThe Content-Type representation header is used to indicate the original media type of the resource

"customFields" object - store test run custom fields

It is possible to import test run custom field values into the Test Run object. Xray will use the "id" to find the existing test run custom field in the project settings.

idThe test run custom field ID
valueThe test run custom field value

Xray JSON Schema

The JSON results file must comply with the following JSON Schema:

{
  "$id": "XraySchema",
  "type": "object",
  "properties": {
    "testExecutionKey": {
      "type": "string"
    },
      "info": {
      "type": "object",
      "properties": {
        "project": {
          "type": "string"
        },
        "summary": {
          "type": "string"
        },
        "description": {
          "type": "string"
        },
        "version": {
          "type": "string"
        },
        "revision": {
          "type": "string"
        },
        "user": {
          "type": "string"
        },
        "startDate": {
          "type": "string",
          "format": "date-time"
        },
        "finishDate": {
          "type": "string",
          "format": "date-time"
        },
        "testPlanKey": {
          "type": "string"
        },
        "testEnvironments": {
          "type": "array",
          "items": {
            "type": "string"
          }
        }
      },
      "additionalProperties": false
    },
    "tests": {
      "type": "array",
      "items": {
          "$ref": "#/definitions/Test"
      },
      "minItems": 1,
    }
  },
  "additionalProperties": false,
 
  "definitions": {
 
    "Test": {
      "type": "object",
      "properties": {
        "testKey": {
          "type": "string"
        },
        "testInfo": {
          "$ref": "#/definitions/TestInfo"
        },
        "start": {
          "type": "string",
          "format": "date-time"
        },
        "finish": {
          "type": "string",
          "format": "date-time"
        },
        "comment": {
          "type": "string"
        },
        "executedBy": {
          "type": "string"
        },
        "assignee": {
          "type": "string"
        },
        "status": {
          "type": "string"
        },
        "steps": {
          "type": "array",
          "items": {
            "$ref": "#/definitions/ManualTestStepResult"
          }
        },
        "examples": {
          "type": "array",
          "items": {
            "type": "string",
            "enum": ["TODO", "FAIL", "PASS", "EXECUTING"]
          }
        },
        "iterations": {
          "type": "array",
          "items": {
            "$ref": "#/definitions/IterationResult"
          }
        },
        "defects": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "evidence": {
          "type": "array",
          "items": {
            "$ref": "#/definitions/EvidenceItem"
          }
        },
        "evidences": { // DEPRECATED
          "type": "array",
          "items": {
            "$ref": "#/definitions/EvidenceItem"
          }
        },
        "customFields": {
          "$ref": "#/definitions/CustomField"
        }
      },
      "required": ["status"],
      "dependencies": {
        "evidence": {
          "not": { "required": ["evidences"] }
        },
        "evidences": {
          "not": { "required": ["evidence"] }
        },
        "steps": {
          "allOf": [
            {
              "not": { "required": ["examples"] }
            },
            {
              "not": { "required": ["iterations"] }
            }
          ]
        },
        "examples": {
          "allOf": [
            {
              "not": { "required": ["steps"] }
            },
            {
              "not": { "required": ["iterations"] }
            }
          ]
        },
        "iterations": {
          "allOf": [
            {
              "not": { "required": ["steps"] }
            },
            {
              "not": { "required": ["examples"] }
            }
          ]
        }
      },
      "additionalProperties": false
    },
 
    "IterationResult": {
      "type": "object",
      "properties": {
        "parameters": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "name": {
                "type": "string"
              },
              "value": {
                "type": "string"
              }
            },
            "additionalProperties": false
          }
        },
        "status": {
          "type": "string"
        },
        "steps": {
          "type": "array",
          "items": {
            "$ref": "#/definitions/ManualTestStepResult"
          }
        }
      },
      "required": ["status"],
      "additionalProperties": false
    },
 
    "ManualTestStepResult": {
      "type": "object",
      "properties": {
        "status": {
          "type": "string"
        },
        "comment": {
          "type": "string"
        },
        "evidences": {
          "type": "array",
          "items": {
            "$ref": "#/definitions/EvidenceItem"
          }
        },
        "defects": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "actualResult": {
          "type": "string"
        }
      },
      "required": ["status"],
      "additionalProperties": false
    },
 
    "TestInfo": {
      "type": "object",
      "properties": {
        "summary": {
          "type": "string"
        },
        "description": {
          "type": "string"
        },
        "projectKey": {
          "type": "string"
        },
        "requirementKeys":  {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "labels": {
          "type": "array",
          "items": {
            "type": "string"
          }
        },
        "testType": {
          "type": "string"
        },
        steps: {
          type: "array",
          items: {
            type: "object",
            properties: {
              action: {
                type: "string"
              },
              data: {
                type: "string"
              },
              result: {
                type: "string"
              }
            },
            required: ["action"],
            additionalProperties: false
          }
        },
        "scenario": {
          "type": "string"
        },
        "scenarioType": {
          "type": "string"
        },
        "definition": {
          "type": "string"
        }
      },
      "dependencies": {
        "steps": {
          "allOf": [
            {
              "not": { "required": ["scenario"] }
            },
            {
              "not": { "required": ["definition"] }
            }
          ]
        },
        "scenario": {
          "allOf": [
            {
              "not": { "required": ["steps"] }
            },
            {
              "not": { "required": ["definition"] }
            }
          ]
        },
        "definition": {
          "allOf": [
            {
              "not": { "required": ["steps"] }
            },
            {
              "not": { "required": ["scenario"] }
            }
          ]
        }
      },
      "required": ["summary", "projectKey", "testType"],
      "additionalProperties": false
    },
 
    "EvidenceItem": {
      "type": "object",
      "properties": {
        "data": {
          "type": "string"
        },
        "filename": {
          "type": "string"
        },
        "contentType": {
          "type": "string"
        }
      },
      "required": ["data", "filename"],
      "additionalProperties": false
    },
 
    "CustomField": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "id": {
            "type": "string"
          },
          "value": {}
        },
        "required": ["id", "value"],
        "additionalProperties": false
      }
    }
  }
}


Example 1: Importing gherkin and other test results

In this example, we are importing execution results for three existing test issues in Jira. The last issue DEMO-9 must be a BDD Test with a Gherkin definition because the results contain examples. The remaining issues can be of any test type.

{
    "tests" : [
        {
            "testKey" : "DEMO-7",
            "start" : "2013-05-03T11:47:35+01:00",
            "finish" : "2013-05-03T11:50:56+01:00",
            "comment" : "Test was OK but the performance is very poor",
            "status" : "PASS"
        },
        {
            "testKey" : "DEMO-8",
            "start" : "2013-05-03T12:14:12+01:00",
            "finish" : "2013-05-03T12:15:23+01:00",
            "comment" : "Performance was better this time, in the context of test set DEMO-10.",
            "status" : "PASS"
        },
        {
            "testKey" : "DEMO-9",
            "start" : "2013-05-03T12:19:23+01:00",
            "finish" : "2013-05-03T12:20:01+01:00",
            "comment" : "Error decreasing space shuttle speed.",
            "status" : "FAIL",
			"examples" : [
				"PASS",
				"PASS",
				"PASS",
				"PASS",
				"PASS",
				"FAIL"
			]
        }
    ]
}

Example 2: Generic Test

This is a simple example of a JSON file with execution results for a generic test.

{
    "tests" : [
        {
            "testKey" : "ABC-129",
            "start" : "2014-08-30T11:47:35+01:00",
            "finish" : "2014-08-30T11:50:56+01:00",
            "comment" : "Successful execution",
            "status" : "PASS"
        }
    ]
}

Example 3: Importing manual test results with steps

This is a simple example of a JSON file with execution results for a manual test.

{
    "tests" : [
        {
            "testKey" : "DEMO-57",
            "start" : "2014-08-30T12:19:23+01:00",
            "finish" : "2014-08-30T12:20:01+01:00",
            "comment" : "Error executing step 2!",
            "status" : "FAIL",
            "steps": [
                {
                    "status": "PASS",
                    "actualResult": "Step 1: OK"
                },
                {
                    "status": "FAIL",
                    "actualResult": "Step 2 *Failed* with an unexpected error message",
                    "evidences" : [
                        {
                            "data": "(... base 64 encoded ...)",
                            "filename": "screenshot1.jpg",
                            "contentType": "image/jpeg"
                        }
                    ]
                }
            ]
        }
    ]
}

Example 4: Importing test results with Test Run Custom Fields

This is a simple example of a JSON file with execution results with Test Run Custom Fields values.

{
	"info": {
		"summary": "Execution of automated tests for release v1.3",
		"description": "This execution is automatically created when importing execution results from an external source",
		"user": "admin",
		"startDate": "2014-08-30T11:47:35+01:00",
		"finishDate": "2014-08-30T11:53:00+01:00"
	},
		"tests": [
			{
				"testKey": "DEMO-25",
				"start": "2014-08-30T11:47:35+01:00",
				"finish": "2014-08-30T11:50:56+01:00",
				"comment": "Successful execution",
				"status": "FAIL",
				"customFields": [
					{
						"id": 1,
						"value": "true"
					},
					{
						"id": 2,
						"value": "13400"
					},
					{
						"id": 3,
						"value": "Test instance is refreshed"
					}
				]
			}
		]
}

Example 5: Importing data-driven manual test results with auto-provisioning of tests

This is an example of a JSON file with a single test result.

This is a data-driven manual test with two iterations. For each iteration, we provide the parameters and the step results.

Xray will also create or update the test in Jira with the specification contained on the "testInfo" object.

{
    "tests": [
        {
            "start" : "2021-08-30T11:47:35+01:00",
            "finish" : "2021-08-30T11:50:56+01:00",
            "comment" : "Successful execution",
            "status" : "PASS",
            "evidence" : [
                {
                    "data": "iVBORw0KGgoAAAANSUhEUgAABkIAAAO9CAYAAADezXv6AAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAJcEhZcwAAEn(...base64 file enconding)",
                    "filename": "image21.jpg",
                    "contentType": "image/jpeg"
                }
            ],
            "testInfo": {
                "summary": "Strong password validation",
                "type": "Manual",
                "projectKey": "STORE",
                "steps": [
                    {
                        "action": "Open the Change Password screen by selecting option \"My Profile > Password\"",
                        "data": "",
                        "result": ""
                    },
                    {
                        "action": "Fill the password fields with data",
                        "data": "Current Password: ${Password}\nNew Password: ${Password}\nConfirm New Password: ${Password}",
                        "result": "The new password is: ${Valid}\nError:\n${Message}"
                    }
                ]
            },
            "iterations": [
              {
                "parameters": [
                    {
                        "name": "Password",
                        "value": "2635ftvu23v7t!09"
                    },
                    {
                        "name": "Valid",
                        "value": "Valid"
                    },
                    {
                        "name": "Message",
                        "value": ""
                    }
                ],
                "status": "PASS",
                "steps": [
                    {
                        "actualResult": "",
                        "status": "PASS"
                    },
                    {
                        "actualResult": "Password changed successfully",
                        "status": "PASS"
                    }
                ]
              },
              {
                "parameters": [
                    {
                        "name": "Password",
                        "value": "123123"
                    },
                    {
                        "name": "Valid",
                        "value": "Not Valid"
                    },
                    {
                        "name": "Message",
                        "value": "Password is too simple."
                    }
                ],
                "status": "FAIL",
                "steps": [
                    {
                        "actualResult": "",
                        "status": "PASS"
                    },
                    {
                        "actualResult": "Password too simple!",
                        "status": "FAIL"
                    }
                ]
              }
            ]
        }
    ]
}

Importing Multiple Execution results

Xray supports importing multiple results for the same Test issues in the same execution. These results often indicate different contexts/environments where the same Test must be executed. Xray will group all executions of the same Test in a single Test Run and present all execution information, including the different contexts in the Execution page. 


When importing execution results using the Cucumber JSON output formatter, multiple executions for the same scenario/Test issue will be merged into a single Test Run.

When importing execution results using the Xray JSON format, the results JSON element must contain all execution results for the same Test Run.

Xamarin Test Cloud

If you are using the Xamarin Test Cloud for executing Cucumber mobile Tests in different combinations of mobile devices and operating systems, you can import the results to Jira by making a compressed zip file containing the multiple Cucumber JSON files.