Wsrtjtyk

My project using RequestsLibrary to do interface automation, and all interface calls share a session, which is the session generated by the [Create Session] function.

On this basic, we want to do concurrency, using pabot, and the way we want to use is: all multi-threads share a session for concurrency, so the [Create Session] function is currently called only once, and then all threads share the session.

The session can be retrieved from multithreads in my test , but when the interface is invoked, it is found that other thread interface requests fail：

error messages:

KEYWORD RequestsLibrary . Get Request ${agent.session}, ${uri}, headers=${header}, timeout=${timeout}

Documentation:  

Send a GET request on the session object found using the



Start / End / Elapsed:  20181109 15:06:36.520 / 20181109 15:06:36.523 / 00:00:00.003

15:06:36.523    FAIL    Non-existing index or alias 'adminsession'.

So I would like to ask if we support concurrent scenarios?

The way that Pabot creates parallel processes is to start multiple independent instances of Robot Framework. In each instance you'll have a separate instantiation of the RequestLibrary. As a consequence of this you'll not be able to share the same session.

Although It is possible to share values from instance to another instance through the pabotlib, this doesn't work for objects. Often an object can be serialized into a string, but sadly the Requests module that RequestsLibrary depends on doesn't support this.

In my view the best approach is to recreate identical sessions across the sessions by reusing the same cookies and other session specific variable via pabotlib.