Hi all, I have tried simple test case “get topology” with robot request library and it also works pretty neat: *** Settings *** Library Collections Library RequestsLibrary

I like the word “test” on integration root, now what are the things we will have under test? Maybe tools that can be used by any test (like your scripts) and then the test themselves (CSIT,

Thanks punal and luis! It is a good lib that uses the python requests library and provides api for the robot framework. The lib was evaluated before we try to find other solutions, and we think it a

Hi all, Please check today’s meeting MoM at: https://wiki.opendaylight.org/view/CrossProject:Integration_Group:Meetings#Meeting_Minutes_of_Group_1 BR/Luis

Can anyone try thisrobotframework-requests vs CSIT-test-tool requests and see what are the differences? I would like to try in the Ericsson Lab today if I have time….

Hi Team, We can use robotframework-requests https://github.com/bulkan/robotframework-requests We are using “requests” right now in CSIT test tools but robotframework-requests will

Sure, luis, how about the following? Integration -- distributions packaging test -- tool

Hi Baohua, I have not really thought much on the name but yes we need a folder for all that is test code (python, robot, etc..), so one idea is to have the following structure under integration:

Yes, luis. Definitely. What I concern is should we put the code now or wait until the code is more stable? As Deng hui and I are still fixing one little bug. After that, we can see the basic release

Ok. I understand your concern now. I'll let Baohua and Denghui push to the ODL repo since they have done the work to create these tests :) -Moiz

Hi Moiz, My only concern was that the existing verify job will build the release vehicles every time someone changes something in the test code, I do not know how much effort/time is required for

Thanks for your feedback, Luis. It would be of great help if widely thorough tests can be done in various environment, before we make the code stable. As we agreed before, I will notify every stable

When you push code into the repository it will trigger a verify build. However if you do not have your integration tests integrated into the maven build then they will not be run. Was your concern

Just sent the mail and I found this link: https://github.com/bulkan/robotframework-requests This is maybe what we need for REST requests in Robot…

Hi Carol and Punal, I checked the Robot framework using the wiki instruction Carol wrote and I liked very much, specially how clear and easy is to write a test case (SimpleTest.txt) and the

Hi Moiz, just a question: our repo as it is configured now, should not trigger a verify build job whenever someone tries to put something on it (i.e. with git push)? or is there another way to do

How about just adding the python scripts into the integration repo instead of using github. It doesn't hurt. -Moiz

Hi guys, Congratulations, I downloaded the python scripts to the test tools VMs, changed the controller IP and run the system test with no issues. I saw you coded very well all the REST requests

Thanks Andy for your quick answer. The question comes because we have different stuff in our git repo : /distributions: this is what Ed created to build the controller release vehicles /packaging:

What jenkins builds is completely dependent up where it's pointing from the git branch options as well as the gerrit path triggers. So, yes, it's feasible to have different jobs for different