Hey everyone, I’m looking for some advice on streamlining our test case import process for Jira Xray. Right now, it’s eating up a lot of time that could be spent on actual testing.
Our current setup involves an Xray repository that requires a specific XML structure for input. We have to create an Excel file for each new story, which is pretty time-consuming.
Has anyone found a workaround or a more efficient way to handle this? I’m wondering if we need a programmatic solution or if there’s a simpler method I’m overlooking.
I’ve been thinking about ways to automate the process, especially for the preconditions and steps, since they need to be context-aware. It would be great if Atlassian could implement an AI solution for generating Xray test cases from stories.
Any tips or experiences you could share would be super helpful. Thanks in advance!
Having faced similar challenges, I can share a strategy that proved effective for our team. We implemented a custom Jenkins job that integrates with our version control system. This job automatically generates Xray-compatible XML files from our test case specifications, which are maintained in a structured format within our codebase. The XML files are then pushed directly to Jira using Xray’s REST API.
This approach eliminated the need for manual Excel file creation and significantly reduced the time spent on imports. It also improved consistency across our test cases and allowed for easier version tracking. While setting up the initial pipeline required some effort, the long-term benefits in terms of time savings and reduced human error have been substantial. It might be worth exploring a similar automated solution tailored to your specific workflow and tools.
I’ve been in your shoes, John, and I can definitely relate to the frustration of manual test case imports.
In my experience, investing time in a custom script or tool has paid off enormously. We developed a Python script that interfaces with Jira’s API to automate our test case imports. Although we still used Excel as a starting point, we standardized the template considerably, which allowed the script to generate the XML structure that Xray expects. This change reduced our import time by about 70%.
Additionally, setting up a library of reusable test case components has helped streamline the process further by reducing repetitive work when assembling new stories. While the initial setup requires effort, the subsequent time savings have been significant. Hope this offers some valuable insights.