Jira Xray produces a test execution without associating imported Cucumber JSON cases. Verify your configuration using the examples below:
Execution Setup:
{
"config": {
"projectCode": "XYZ01",
"headline": "Execution for Cucumber Tests",
"details": "Run for validating Cucumber outcomes",
"issueType": { "code": "20001" }
}
}
Feature File Example:
[
{
"filePath": "spec/Login.spec",
"scenarios": [
{
"scenarioName": "Valid login scenario",
"actions": [
{ "description": "open login page", "status": "pass" },
{ "description": "submit correct details", "status": "pass" }
]
}
]
}
]
I encountered a similar problem while integrating Cucumber JSON test cases with Jira Xray. In my case, the linkage issue was due to mismatched identifiers between the JSON output and the Xray test execution configuration. I spent quite a while reviewing the documentation and realized that ensuring the consistency of scenario names and test keys was crucial. After aligning the JSON fields with the expected configuration, the test executions became properly linked. It is advisable to validate all field mappings and double-check your JSON structure against the guidelines provided in the documentation.
Based on my experience, this issue often results from discrepancies between the JSON fields and what Xray expects. Ensuring that the test case identifiers are consistent across the configuration and the feature files is crucial. I found that even minor misconfigurations, such as extra spaces or case sensitivity in the test keys, can cause the cases to remain unlinked. It might be helpful to manually review a sample import against the documentation and run a controlled test initially. Adjust the configuration accordingly until the linkage occurs as expected, and consider updating to the latest version if problems persist.
i had similar issues due to incosistent test key strings. even small spacing or case errors in your json can cause the cases to not link. double check yer identifiers and config details to make sure everything exactly matches the docs.
After experimenting with similar linkage issues, I discovered that one potential pitfall was the ordering of configuration entries within the JSON file. My earlier attempts failed because even minor formatting details affected the mapping between the Cucumber file and Xray’s expected structure. I had to carefully adjust whitespace and confirm the alignment of test identifiers, which eventually resolved the disconnection. Troubleshooting step by step with smaller test imports helped isolate the exact mismatch, leading to a more stable integration after updating the configuration details.