Hi all,
The testing tool that i am currently using is the robot framework. I am using both the test case name and also the documentation tag to increase the readability of the test.
As a user of robotfamework xray REST import interface, I want to add the "[Documentation]" documentation tag as the test ticket description.
Usually this field also contains relevant information that can be easily imported/used as well.
Is it possible to do so? Is there any way to do that?
Best Regards,
Pedro
We do have a very complete documentation that helps users work with Robot and Robot framework, which are mainly the documentations Taking Advantage of Robot XML Reports and
Importing Execution Results Robot.
With those documentations you can find a way to import your data into Xray and notice that, for the Multipart Robot import results, we have the capability to create Test and Test Execution field data:
Xray provides another endpoint if you want to create new Test Executions and have control over newly-created Test Execution and Test fields. It allows you to send one XML file (the Robot report) and a JSON similar to the one Jira uses to create new issues.
This should cover your needs but please contact our support if you have any further questions on the matter.
Best Regards,
Team Xray
I think I as not completly clear in my question. I am able to import the test to XRay and that process is working fine.
What I want is to map in a easy way the [Documentation] tags inside a Robot Test Case as the description of the test. Is there any way to map fields of robot framework execution result into a ticket in a custom way? I do not want to do that one by one. I want to that to be a rule of the import.
Thank you for the reply,
Pedro
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.
Hi @José Domingues _Xray and @Diamantino Campos
We expect these features to be transferred to XRAY Integration. The problem is similar XRAYCLOUD-3408. All the features have been created for the JUnit extension format, but these features should definitely be applied to other formats. While completely converting the test part to an automatic structure, it is necessary to write different scripts for some basic points and to reach more than one endpoint.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Pedro_Rodrigues and @seda_gurocak
Currently, Xray does not have those features, however, we have these two improvement suggestions that should address your needs:
https://jira.getxray.app/browse/XRAY-7949
https://jira.getxray.app/browse/XRAY-5694
Please *Vote* so we can keep track of your interest and *Watch* to receive news on the Suggestion.
Kind regards,
Rogerio Paiva [Xray Support Team]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.