JIRA and Robot Framework

[da...@ecomp.co.uk]

Hi all, 

I'm running Robot Tests through Jenkins and want to be able to change the corresponding ticket status in JIRA. I found JiraRobot, can this do it? Is this the best way? 

Thanks,

David

[adam.wyp...@gmail.com]

Hi David, 

you need to check by yourself, but base on current keywords in library you can only add comment or assign somebody to Jira ticket. In my opinion updating JIRA using automatic test smells for me - in example: what will be happen if your test will fail due to environment problem? I think test should do own job to prove that functionality works and tester should update JIRA ticket if corresponding tests passed.

Best Regards,

-Adam.

[Alex C.]

XRAY for Jira can be used for integrating with robot-framework.

[Abhishek Ganotra]

Alex, 

Could you please share the steps on how to upload result file generated by Robot after execution on xray test execution?

I am trying to implement the same.

[Anne kootstra]

This can be learned from the X-Ray documentation: 

https://confluence.xpand-it.com/display/XRAY/Integrating+with+Testing+Frameworks

https://confluence.xpand-it.com/display/XRAY/Testing+using+Robot+Framework+integration+in+Python+or+Java

https://confluence.xpand-it.com/display/XRAY/Import+Execution+Results+-+REST#ImportExecutionResults-REST-RobotFrameworkXMLresults

Kind regards,

Anne

Op dinsdag 4 december 2018 06:45:15 UTC+1 schreef Abhishek Ganotra:

[Abhishek Ganotra]

Thanks for replying. 

I did try using the same steps mentioned on the link. 

I ran a curl command and I am also project admin where I am trying to upload the results.

curl -H "Content-Type: multipart/form-data" -u admin:admin -F "file=@output.xml" http://yourserver/rest/raven/1.0/import/execution/robot?testExecKey=XNP-23

instead of output.xml I am giving complete path to xml for example "c:/user/temp/ride/output.xml"

and yourserver gets replaced by server I am using and testexeckey gets replaced by my original test execution key.

[Hi-Fi]

One option is to use https://github.com/Hi-Fi/robotframework-statusupdater, that uploads results per test case (so progress is visible all the time in Xray).

[Anne kootstra]

I'm assuming you're the creator. Is this purely a plugin for Jenkins, or also a Listener library for Robot Framework? I'm assuming it is, but then then there is a dependency on Jython? 

Kind regards,

Anne

Op woensdag 5 december 2018 06:06:12 UTC+1 schreef Hi-Fi:

[Hi-Fi]

Hi,

It's library for Robot made by me, and requires running either tests with Jython or utilizing library as Remote. 

It depends also what is needed: Realtime status in Jira/QC/other test management tool is possible to get with mentioned library, and pushing while xml at the end provides status to system, just a bit slower way. And when pushing whole xml, it still might require some parsing of the system can't parse that itself.

Br,

Juho

[dmitriy.c...@rallyhealth.com]

Trying to understand the big picture... OK, once you ran the test, updated JIRA ticket status, what happens to the test? JIRA ticket gets closed, and the test that updates the ticket is no longer needed. What I'm hinting at is that test automation is used for tests that will need to be re-run over time, multiple times. So the life cycle of your test is limited by the life cycle of your ticket. 

I mean, if it's worth for your organization to write automation per ticket and then discard it, go for it...  If a JIRA ticket in question is going to stay open for a while and you need testing in the meantime maybe... In a TDD of a web app situation you could possibly even track the progress of a feature development by running a long scenario and see what failed. 

If you want to keep you test code for regression testing after JIRA ticket is closed you will need to remove JIRA updating code from each test. Seems like a lot to keep track of. As another user suggested, why not let the human update tickets? 

[Jirayu Kaewprateep]

Do you have the interfaces spec. on hand?