18 January 2026:
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
This forum is now archived and is in read-only mode. Please continue discussions on our improved new Sahi Pro Community forum.
Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, API, windows and java based applications and SAP.
VERY SLOW Application Causes Scripts to Time Out BEFORE They Start
i_love_sahi
Members
OS = Windows XP service pack 3
Browser = Internet Explorer 8
Sahi Open Source
Version : V3.5
Build : 2011-05-25
I'm running tests against a site that is very slow. Sometimes it loads in about 30 seconds, sometimes it loads in about 3-4 minutes. Under certain configuration settings, it can take over eight minutes for it to load. This is acceptable and expected behavior.
On an initial page load, when I click "set" via the Sahi controller, before starting the script, this long wait can cause Sahi to silently time out, so that clicking "start" does not do anything. I have observed similar behavior when running test suites, where scripts often "fail" due to an error that says:
ERROR
Script did not start within 600 seconds. at Sep 5, 2012 10:21:56 AM
An identical error is observed when attempting and failing to run a script from the Sahi controller.
The page takes so long to load because it is waiting on AJAX calls. I need Sahi to wait longer instead of timing out. It used to give me errors saying that the script timed out in 150 seconds, so I changed sahi.properties like so:
#Number of cycles Sahi will wait for the page to load before it proceeds with execution
#Time spent is (script.max_cycles_for_page_load x script.time_between_steps) milliseconds
script.max_cycles_for_page_load=5700
This configuration fixed a problem I was having when the scripts time out during execution AFTER they started, but it did not fix the issue of scripts timing out BEFORE they started.
Browser = Internet Explorer 8
Sahi Open Source
Version : V3.5
Build : 2011-05-25
I'm running tests against a site that is very slow. Sometimes it loads in about 30 seconds, sometimes it loads in about 3-4 minutes. Under certain configuration settings, it can take over eight minutes for it to load. This is acceptable and expected behavior.
On an initial page load, when I click "set" via the Sahi controller, before starting the script, this long wait can cause Sahi to silently time out, so that clicking "start" does not do anything. I have observed similar behavior when running test suites, where scripts often "fail" due to an error that says:
ERROR
Script did not start within 600 seconds. at Sep 5, 2012 10:21:56 AM
An identical error is observed when attempting and failing to run a script from the Sahi controller.
The page takes so long to load because it is waiting on AJAX calls. I need Sahi to wait longer instead of timing out. It used to give me errors saying that the script timed out in 150 seconds, so I changed sahi.properties like so:
#Number of cycles Sahi will wait for the page to load before it proceeds with execution
#Time spent is (script.max_cycles_for_page_load x script.time_between_steps) milliseconds
script.max_cycles_for_page_load=5700
This configuration fixed a problem I was having when the scripts time out during execution AFTER they started, but it did not fix the issue of scripts timing out BEFORE they started.
Comments
#No of times Sahi should wait for stability of AJAX and page loads before continuing. min value is 1
script.stability_index=15
but I could not understand exactly what it was doing. It did seem to be related to the time between "setting" a script from the controller and the time between "starting" a script from the controller, but I couldn't figure out how it worked. Does anyone know?
Or
use _wait(timelimit) function in the script.