Skip to content
Vess Popov edited this page Aug 10, 2020 · 2 revisions

Note: By default, R sessions in Concerto are serialized. This greatly improves performance, by releasing the resources taken up by the R session as soon as possible and reducing memory usage. You can change the test runner to be unseralized from the Admin Tab in Concerto panel.

The basic principle with session resuming is that we want to know who is running the test so we can resume their previous session. A simple way to enable session resuming is to add a startSession node, tick the 'Resumable?' box and then pass the user entity to this node. This feature of the startSession node works by serializing the user's session state to a file before each new page in the test is shown. The next time the same user comes to that startSession node (i.e. they come back to the beginning of the test execution flow), the node checks whether this user has an ongoing session. If they do, it will deserialize their session and resume the test from where they left off.

It is up to you as the test developer what the user entity contains, and how/whether it should be authenticated. You can make the session resumable by cookie, or by HTML parameter, or by authentication with user and password.

Clone this wiki locally