nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible for the linked tickets in Xray to automatically receive the same status as the ticket

Marieta Uzunova

Hi all,

I am currently importing my test results from Robot Framework to Xray. However, I have three test cases in Xray that I cover with just one test case in Robot Framework. It is not desired to merge these three test cases into one. I was thinking that maybe I could link the three test cases together, so the status would automatically be set for all three. Is this possible?

P.S.: I thought about creating automation rules, but the status options "To Do", "Pass", or "Fail" are not available. I would greatly appreciate any help.

Thank you

Accepted answers

All comments

Valerie Knapp_dpp5c6

Hi @Marieta Uzunova , welcome to the Atlassian Community and thanks for your question.

Even though the Xray issue types exist as issue types in Jira, I fear that the data from the Xray app itself isn't accessible to the Jira automation. I have had similar issues with other apps, like Tempo, where you want to automate something in the app data, but this is only possible if the app has automation in it.

I would always recommend two things in situations like these,

1) Check the documentation for help - https://docs.getxray.app/site/xray

2) Contact the vendor of Xray by opening a ticket with your query - https://marketplace.atlassian.com/apps/1211769/xray-test-management-for-jira?hosting=cloud&tab=support

You didn't indicate if you were using DC or Cloud but your screen looks like DC to me. I also tagged the app of Xray into this post so hopefully more people who are experienced in this app can chime in.

Good luck and don't hesitate to share other info or feedback here by writing a comment.

Cheers

Stefan Salzl

Hi @Marieta Uzunova

re-asking for clarification as it sound a bit confusing for me:

are really talking about test cases? To do, passed, failed sound very familiar to me for test runs (which are the executed instances of a testcase within a test execution issue).

It‘s very important to be clear in the terminology.

Could you maybe provide a more detailed step my step explanation? Maybe supported by example issue names and types and/or maybe even screenshots. Everything that might help get a deeper understanding of the problem in order to find the right solution.

Best
Stefan

Manuel_u1i996

Hi @Marieta Uzunova ,

that's an unusual scenario; not sure the reason for having that.

If I got it right, you have 1 Robot Framework test case that in practice is doing what those 3 Tests in Xray are supposed to do?

You could annotate the RF test with the 3 test issue keys but I don't think that works, because it's not really a common scenario and Xray won't process all those tags (I think).

Using Automation from Jira, it's not possible to implement rules like that as there are no means to interact with Xray data in that detail, at least at this moment.

My strong recommendation is to actually split the current RF test into 3 RF tests, so you can have a one-to-one mapping. Note: I'm assuming those 3 test cases in Xray make sense to exist as such.

Marieta Uzunova

Hi Stefan,

Sorry, I just saw your message. I’ll try to explain the problem more clearly. In the screenshot, you can see what my test looks like. This test consists of three test cases. These three test cases are present in Xray.

I set it up this way to reduce duplicate tests and save time. The actual issue is with transferring the results. When I want to automatically transfer the result to Xray, it only takes the test that is recorded on the day.

See the second screenshot. I tried to fix the issue. It worked for this single test case, but when I run multiple test cases together, only the first test case works, and the rest fail because the application isn’t closed and then times out.

I look forward to your response.

Marieta

Marieta Uzunova

Hello Manuel,

thank you for your response. However, if I split one test into three test cases as they are in Xray, it will take a lot of time to run the automated regression test

Marieta

Manuel_u1i996

I understand but that is more an indicator of how the test automation is built.. maybe they are testing too much if you have smaller, focused tests, you'll have more control and you will be able to understand their impacts more clearly whenever they fail.

Stefan Salzl

Hi @Marieta Uzunova

first of all I need to assume that I´m not familiar with Robot Framework itself but with other similar frameworks.

As far as I can follow your description it´s not an xray problem itself but a problem in the testcase design within the robot test suit. As the error message points out a test case needs a dedicated "end" like a teardown in order to switch to the next test case.

Furthermore the "Tag" in the test case always is a connector to the requirement (hence Story) that the testcase covers. It´s not a mapping to an eventually already existing test case. after a first import of a test result file the related test cases are created automatically

I heartly recomment to read throug the dedicated documentation page from xray how to use robot framework with xray:

https://docs.getxray.app/display/XRAYCLOUD/Testing+using+Robot+Framework+integration+in+Python+or+Java

Best
Stefan

Stefan Salzl

Hi @Marieta Uzunova

Is there any further feedback from your side?

If your questions were adresed please consider to hit "Accept Answer" .

Thanks in advance

Best
Stefan

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

xray

jira

addon-com.xpandit.plugins.xray

unknown-hosting-type

jira-unknown-hosting-type