I would advise against mixing robot resource files and python code in the same repository. It is very hard to place resource files in a spot that is reusable to everyone since there is not an easy way to do imports other than ../wherever/resource.robot. And that only gets even harder if you also have to deal with having it in python code.
I am fine with reworking robotframework-onap (the python package that lives in python testing utils) to use the sdk, the less code in there the better. I think we can use a different repo in integration for the other robot code. There are already a few Thanks, Daniel Rose com.att.ecomp / org.onap 732-420-7308 From: [email protected] <[email protected]> On Behalf Of Marek Szwalkiewicz (DT) Sent: Tuesday, June 2, 2020 9:24 AM To: Morgan Richomme <[email protected]>; [email protected] Subject: Re: [onap-discuss] #robot #test ONAP Libraries for Robot Framework Yes, no slot tomorrow, sorry! As for repository - I would like to keep the python-onapsdk wrapper there (Robot Library) but also other shared Robot functions as Robot Resources. In this case having "python" in the name might confuse users. Maybe robot-utils? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21230): https://lists.onap.org/g/onap-discuss/message/21230 Mute This Topic: https://lists.onap.org/mt/74624084/21656 Mute #test: https://lists.onap.org/mk?hashtag=test&subid=2740164 Mute #robot: https://lists.onap.org/mk?hashtag=robot&subid=2740164 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
