Comment #4 on issue 532 by pekka.klarck: Variables should not leak to lower
level keywords
http://code.google.com/p/robotframework/issues/detail?id=532
I think a good plan how to resolve variables in RF 2.6 is this:
1) Don't put variables inside a test or keyword into the scope of the lower
level
keyword.
2) Don't put variables in test, suite, or global level there either.
3) When resolving variables, first look the local scope.
4) If there is no variable in the local scope, look the scopes of the
higher level
keywords and test.
5) If var is found from higher level scopes, use it but show a deprecation
warning.
6) If var still not found, look for it from test, suite, and global scopes
in that order.
7) If no var found, resolving failed.
In RF 2.7 we can then skip steps 4) and 5) altogether.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Subscription settings:
http://groups.google.com/group/robotframework-commit/subscribe?hl=en
