Comment #5 on issue 1660 by kormb...@gmail.com: Remote: support multiple
remote library instances
http://code.google.com/p/robotframework/issues/detail?id=1660
You are correct on possible issues. Close it out if you want.
I have begun work on something I will put on GitHub and PyPI eventually.
It has turned out to be more complicated than I thought.
If implementation returns keyword names in a different convention it should
not matter - myKeyword vs my_keyword.
Should be able to ignore Stop Remote Server because some/most servers will
add this beyond control of library author.
I tried to do run_keyword_on, and found that I could only use RF's
arg-checking if I invoked BuiltIn.Run Keyword. Doing this "properly" would
require the library knowing what alias it has at runtime (in case of
multiple instances), which requires accessing private variables
(EXECUTION_CONTEXTS.current.namespace._testlibs).
I decided to go the other route and have the library look for and process a
kwarg unlikely to collide with the user's library - like
multi_remote_alias=SYSTEM_A. This requires the wrapper to add kwargs to the
argspec if the user's keyword does not have them, so it will be an optional
feature.
Switch Remote Library Instance SYSTEM_B
My Keyword arg1 # execute on current remote (SYSTEM_B)
My Keyword arg1 multi_remote_alias=SYSTEM_A # execute on SYSTEM_A,
but SYSTEM_B is still the current
I will post to user group when I am looking for review.
Thanks.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "robotframework-commit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to robotframework-commit+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
