Issues Encountered Using Remote Library

[yiyang zhang]

I'm using the Robot Framework with a remote library. In my local test cases, I import it as follows:

Library Remote http://10.8.128.16:8270

Within my custom test library, there's a method for SUITE SETUP where I call a Robot built-in method to retrieve the test case path: BuiltIn().get_variable_value("$SUITE SOURCE").

Now, when I execute the local test cases, it throws an error at the point where I'm trying to fetch $SUITE SOURCE: RobotNotRunningError: Cannot access execution context.

When both the test library and test cases are local, everything works fine, and the tests run without issues. Is it possible that using a remote library doesn't support this kind of usage?

[Tomas Pekarovic]

This is intended... As I understand It

remote library is just a black box for the  running robot tests. In your case, you are running it from machine1 that is running robot binary. The execution context is on this machine, where RF is directly running. 

The remote library just wraps some keywords, but It does not know nothing about context in which robot is running. Therefore you can't get use of BuiltIn() library on the remote machine.

I personally did not found a way , how to send context to remote library to be able to just get this information.

--
You received this message because you are subscribed to the Google Groups "robotframework-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to robotframework-u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/robotframework-users/CALkTEfTnpznWpbK3x_trF9DLdeFGbdt1R%3D_n8x_Psj-pROSbRg%40mail.gmail.com.

[David]

This might be an interesting use case to file as an enhancement request to RF framework, to add a way to pass the RF framework's execution context (info) as part of the remote library protocol so that remote library's can implement the support to receive it.