Skip to main content

SeeTestAutomation- Working With Session Ids

info

Please note that this tool is classified as a Legacy tool. We recommend transitioning to our updated solutions to maintain optimal performance and security in your workflows. For more information on this matter, please reach out to technical support .

info

Session ID's allow SeeTest to coordinate between multiple clients (test sessions) This allows SeeTest to run multiple tests on local or remote (SeeTestCloud) devices.

// DO Creating a client who will get a session id from SeeTest.
Client client = new Client(host,port,true);
 
//NOT RECOMMENDED Creating a client who will not receive a session id from SeeTest.
Client client = new Client(host,port,false);

In addition to executing tests individually via its UI, SeeTestAutomation can be used as a server on which you execute tests on a wide set of clients in parallel, thereby maximizing the concurrent utilization of resources. To prevent impairing the integrity of client states or the abuse of license features, SeeTestAutomation provides the mechanism of useSessionID to coordinate the use of shared resources during the simultaneous execution of multiple tests.

Commands Which Release the Session ​

Session IDs and Backward Compatibility of Tests​

The useSessionID mechanism is being introduced with version 7.8. This means that users running tests created in versions of SeeTestAutomation earlier than 7.8 must adapt these tests to run on version 7.8 and higher. The means of adapting such tests are illustrated in the following example for which we give four variations.

Debugging Tests​

To debug test without session timeout, run the test with useSessionID=false.

client = new Client(host,port,false);
client.setDevice("Device A");

When the test is adapted as depicted immediately above, it will also be executable in version 7.8 because the Boolean value controlling the enabling and disabling of the useSessionID mechanism has been set to false (see lines 1 and 3). However, this way of adapting your tests is not recommended, because essentially it circumvents the useSessionID mechanism. Below, following Variation 3, we describe how you can disable this mechanism, if necessary, in an orderly fashion.

To run a test with clients that do not support sessionID in version 10.3 and above, add disable.debug.mode=true to SeeTest's app.properties file.

info

When creating another client, it is important to set a reporter for each client, generate it and to release the client for example:

 @Before
     public void setUp(){
 		client = new Client(host, port, true);
         client2 = new Client(host, port, true);
 		client.setReporter("xml", "reports", "1");
         client2.setReporter("xml", "reports", "1");
 }
  
 @Test
     public void test_1(){
 	-
 	-
 	-
 }
  
 @After
     public void tearDown(){
 		client.generateReport(false);
         client.releaseClient();
         client2.generateReport(false);
         client2.releaseClient();
 }
Last updated on