We can use com.itko.lisa.vse.SharedModelMap in a custom java step to set the key value pair. This can be done in a Startup Testcase/script. The values on SharedModelMap persists until the workstation is restarted (in case of locally staged test suites) or the LISA server is restarted(in case of test suites staged on coordinator).

Usage:

In the startup script - SharedModelMap.put("timestamp","{{Timestamp}}");

In the subsequent test cases - String time = SharedModelMap.get("timestamp");

I would suggest this way. In a test suite consider complete.tst where you wanted to get the initial value, call a test suite which perofrms the logic for preforming only the capture of Time stamp value.

From now on if you want to use the timestamp test suite globally, you can go ahead and call this particular suite so that you get the captured value which you have set it initially.

We can use com.itko.lisa.vse.SharedModelMap in a custom java step to set the key value pair. This can be done in a Startup Testcase/script. The values on SharedModelMap persists until the workstation is restarted (in case of locally staged test suites) or the LISA server is restarted(in case of test suites staged on coordinator).

Usage:

In the startup script - SharedModelMap.put("timestamp","{{Timestamp}}");

In the subsequent test cases - String time = SharedModelMap.get("timestamp");

The Shared Model Map is an in-memory hashtable that is managed by the VSE.

The hashtable is in the memory space of the VSE; therefore, technically a process running outside the memory space of the VSE JVM cannot access it.

Assuming you get passed the above, if Test Case 1 places a value on the map, and the JVM is stopped before Test 2 executes the value on the map is no longer available.

Additionally, it is the responsibility of the developer to manage the Shared Model Map.

Stopping/Starting a JVM is the only OOTB technique for clearing out this memory space. All other memory management techniques must be implemented by the development team.

Storing too much information can have a negative effect on the performance of the JVM or require an increase in JVM memory allocation

Please use a Namespace so entries in the map are kept in isolation

Each namespace, by default, is initialized to 256 entries.

I would recommend that you review the Persistent Model Map in your scenario since the data is being passed between test cases and not virtual services. The advantage of the PMM is that data can be set for deletion after 30 days of no access.