You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello,
Our team has been looking to implement Xray in our workflow and we want to be able to run SpecFlow tests in our pipeline.
I've been trying to update my Test Executions from Test Runs, by using the REST API, as specified in your documentation:
- https://docs.getxray.app/pages/viewpage.action?pageId=62269785
- https://docs.getxray.app/display/XRAY/Import+Execution+Results+-+REST
- https://docs.getxray.app/display/XRAY/Import+Execution+Results
But the problem I'm facing is that it keeps generating a new Test Execution for each run, instead of updating the existing one.
The tags seem to be correct, my .json (cucumber) looks quite identical to the one in the docs, but still it keeps making new Test Executions.
I was wondering whether this could be functionality that is only available in the Server+DC version? As we are using the Cloud version of Xray, and the docs of the Cloud version don't really specify this scenario.
Another thing that strikes me is that the docs say: "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." --> But in the cucumber JSON output format, there's no way to specify this, other than using the Tags
If not, I'd be happy to supply more detailed information on my issue.
In order to help you with this, we will need to request some more information, so we suggest that you create a ticket in our support desk so that we can help you the best we can.
Best Regards,
Sérgio Freire, Solution Architect and Testing Advocate @Xray
Personal blog on testing, Agile and software development: https://sergiofreire.com
Follow me on Twitter: https://twitter.com/darktelecom
Hi,
I am also facing the same issue, looking for some help.
Also created a support ticket
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the end, it didn't work out how we wanted to, so we gave up on this way...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.