As a safety measure to prevent tests from running too long after something has gone wrong, Testsigma limits how long a browser can wait for a test to send a new command. As a result of that, a test in Testsigma Labs will terminate if it doesn't receive another command in 90 seconds time i.e if there is an idle time of 90 seconds between two Test Steps.

However, there might be instances or scenarios in your Test where you need to wait for a larger time interval for some operation to complete before performing the next step.

Recently, one of our clients had a requirement where they need to wait for about 5 minutes time before the next step. The scenario is something like this:

"As soon as a transaction is performed, a set of data values needs to be entered into the online ledger or database. A series of complex database manipulations performed during the updation causes it to take a duration of 5 minutes or more. And this updation needs to be verified."

Here's an oversimplification of the steps we need to execute:

1. Perform Test steps to generate and submit the data to the Database.

2. Wait for the specified time for the DB manipulations to complete.

3. Perform consequent Test Step that verifies that the data values submitted in step1 has been inserted successfully.

The specified time in this case is 5 minutes i.e 300 seconds. However, Testsigma labs has a default timeout of 90 seconds and we need to alter this for the Test to complete successfully. For that, we can add the following Desired Capability to the Execution Configuration:

Capability nameData TypeValue

Similar to the above scenario, as a safety measure to prevent tests from running indefinitely, Testsigma Labs limits the duration of tests to 30 minutes by default. Another aspect of this restriction is that in today's conditions where Continuous Testing is a necessity, a Test shouldn't take more than 30 minutes and we should minimize the Test duration wherever possible so as to reduce the feedback time.

In extreme scenarios where we need to override this, we can use the following Capability:

Capability nameData TypeValue