[INTTEST-31] migrate Variables.py to Variables.robot Created: 20/Oct/17  Updated: 20/Oct/17

Status: Open
Project: integration-test
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Low
Reporter: Jamo Luhrsen Assignee: Jamo Luhrsen
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: 1 minute
Time Spent: Not Specified
Original Estimate: 1 minute


 Description   

Current integration/test: csit/variables/Variable.py supports multiple variable names which end up holding the same value. Typically, a generic (or newer) variable is set, and more specific (or older) variables get its value, for example CONTROLLER is set to value of ODL_SYSTEM_IP.

Robot supports setting variables on pybot invocation using -v option. This overrides values in Variables.py or in any Variables table in robot files. So if a user has a suite which uses ODL_SYSTEM_IP and tries to invoke it locally (not on RelEng or Sandbox), "-v ODL_SYSTEM_IP:<some_ip>" works.
But the override only happens after applying Python variable files, so if the suite uses a Resource which still refers to CONTROLLER, it will not get the <some_ip> value.

Solution is to move all variable definitions from Variables.py to Variables.robot, in which case CONTROLLER would be set properly.



 Comments   
Comment by Jamo Luhrsen [ 20/Oct/17 ]

I'll try to push a small patch or two every week or so to make progress on this. first example:

https://git.opendaylight.org/gerrit/#/c/64578/

Generated at Wed Feb 07 20:04:23 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.