15:00:51 #startmeeting Robot Happy Hour 15:00:51 Meeting started Wed Jun 10 15:00:51 2015 UTC. The chair is catohornet. Information about MeetBot at http://ci.openstack.org/meetbot.html. 15:00:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:51 The meeting name has been set to 'robot_happy_hour' 15:27:14 (08:19:06 AM) catohornet: Hi As projects are now in the test creation phase they may find some part of functionality is not quite ready but you want to have tests ready to test the functionality when ready. You can use tags to omit these test cases by assigning criticality to them. 15:33:14 hello. any bash script gurus in here? 15:33:17 https://gist.github.com/5075b59e9ddfc9a3a6ba 15:34:05 in the gist above, I'd like to use line #18... but it does not work; line 19 does but it is ugly and stup*d :) 15:34:18 any ideas? 15:36:17 catohornet: so I have a bunch of robot tests running locally, I also have some jenkins jobs that should run these tests and have been able to push them to the sandbox. 15:36:32 catohornet: Generally do people run jenkins jobs that test robot scripts in the sandbox and if so how to do both together. 15:37:05 before they are merged 15:40:14 mgkwill: Yes, by robot scripts you mean robot testsuite files or actual python scripts that point to a robot testsuite? 15:40:54 my files are python libraries and some robot.txt that use them 15:41:04 catohornet: ^^ 15:41:34 catohornet: there are also testplans 15:44:26 catohornet: is there some doc that explains how to test robot suites with jenkins jobs holistically? 15:44:34 mgkwill: all these files should be placed in the appropriate folder under integration tests when you create them. After cloning the integration repo you will have resource folders under test/csit. these are libraries, etc 15:46:12 mgkwill: So you all your libraries, testsuites, and resource files should be located there. Then you import them as resource in your testsuite. Is this how you're accessing the libraries you created for your tests? 15:47:13 catohornet: Yes. I understand the basics behind running and creating robot tests, libraries ect. I'm trying to ramp up on how to test my created suite with Jenkins in the sandbox. 15:47:37 mgkwill: there is no doc, to my knowledge, that explain how to test robot suites with jenkins jobs holistically. But I can check. 15:49:21 mgkwill: there is a doc that explain how to run your test suites in the sandbox..on the wiki. Have you soon that doc? 15:55:17 catohornet: apparently not, but I am reading it now: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:System_Test:Step_by_Step_Guide 15:55:17 though it appears to assume the tests are merged first before you can run them in sandbox 15:56:15 mgkwill: taking a look... 15:57:51 catohornet: I think the assumtion is that you create the robot tests and if they run correctly then you merge them to integration and after that you can test out your tests with a jenkins job in the sandbox and then if that works you merge that to builder 15:58:46 mgkwill: Optional - Verify distribution job in the Sandbox It is possible to verify jobs before they are submitted using the Sandbox. For more information check Releng wiki 15:59:40 Yeah that is for jenkins jobs only, so seems to support my previous comment. 16:00:21 hmm. well thanks. I have more info now than I did before. 16:01:22 mgkwill: On the releng page it talks about running your test in the sandbox 16:01:54 mgkwill: I'm wondering if this is helpful to you. If not we need to clarify more so it is helpful. https://wiki.opendaylight.org/view/RelEng:Jenkins#Jenkins_Sandbox 16:04:24 catohornet: That's what I've used to access the sandbox and that is working. Just don't have info on running a robot suite in said jobs that is not merged. 16:07:56 I will ask. Can we continue in email? I have to end this meeting for other integration business :) 16:13:30 catohornet: sure. no problem. Thanks for your help 16:14:05 mgkwill: you"re welcome 16:14:15 #endmeeting