Script did not start within 150 seconds.

Faiyaz

When running suite file, some scripts give message as "Script did not start within 150 seconds."
But it is running individual very well

deepika.srivastava

hi,

Can you tell which browser you are using ? As i'm also getting the similar kind of error in IE but it is working fine on firefox

globalworming

Please check if you accepted the Sahi certificate with the Sahi SSLManager

deepika.srivastava

yes, i have accepted all the certificates . individual scripts are running fine but when trying to run it with suite it is saying scripts did not start in 150 seconds

globalworming

Does the browser open when you start the suite?

deepika.srivastava

yes .. i have 2 scripts in the suite and after running the suite .. 2 browsers are opened with the correct url mentioned in the suite.

deepika.srivastava

Any idea why it is happening?..i'm still facing this issue.
Script not started in 150 seconds

kashif.khan

deepika.srivastava i did found the solution for your problem. They are as follows

1. Run a command prompt with run as administrator privileges.
2. Execute the start_dashboard.bat file found in the folder \sahi\userdata\bin\
3. Now again run a new command prompt with run as administrator privileges.
4. Run the testrunner.bat with usual parameters.

Objective of these steps is that both starting the SAHI and running the scripts should be done with run as administrator privileges. My guess is that you are using either user access control settings of the operating system. Just disable it if you are permitted then restart the system and everything should work fine without needing to run as administrator whenever you run. Hope this helps you!!!

bagsmode

Kashif Khan,

I posted yesterday about not being able to run the testrunner.bat successfully (same type of issue was happening, it would open the browsers but not proceed after that), so when I saw your post, I gave it a try. Interestingly, I was able to get a little farther than I did yesterday (after the first script, the next one yesterday said it didn't even perform a test on the script), where as today, it stated in the logs that it did perform the first step in the script, but it failed on that first step in both the next two scripts and didn't get farther.

After still having failures, I ended up trying the scripts just one at a time to verify that those still worked... but they didn't!! I know they were working yesterday, so I decided to open up the files, and I saw something weird. Before EACH command, there was something new: _popup("blank").

As an example, my original login script was as such:
_setValue(_textbox("uname"), "gbagrowski");
_setValue(_password("pword"), "asdf");
_click(_radio("rb_tkper"));
_click(_submit("Log In"));

But for some reason, I am now seeing:
_popup("blank")._setValue(_textbox("uname"), "gbagrowski");
_popup("blank")._setValue(_password("pword"), "asdf");
_popup("blank")._click(_radio("rb_tkper"));
_popup("blank")._click(_submit("Log In"));

I recall when I was initially testing Opera last night, in which I was having issues, there was one of those browser slider popups that stated that Opera blocked a popup, but there are no popups in any of the code (btw: I don't get this popup block notification in any of the other browsers in which I test the same scripts). So, I'm wondering if Sahi somehow inserted these _popup("blank").'s in the script when it thought that there was a popup??? I know that I've looked at the scripts after they were initially created (since I was curious what the code looked like) and I did NOT see these popup references before. I don't know where they came from, but as far as I can tell, I did not put them in myself.

Either way, once I saw what happened, I:
- recreated the scripts
- opened the scripts and verified that there were no _popup("blank").'s in them
- retried the scripts from the IDE.. success, no problems
- retried the suite from the admin shell.. success!! no problems (Finally : )
- out of curiosity, tried the testrunner.bat WITHOUT admin privileges, and it worked too!!

bagsmode

my problem was for all browsers... but I think the core of my problem was that I think I tried redoing the scripts in Opera which was having an issue with testrunner in that it was thinking that when the previous test script killed the browser, that the session closed abnormally, and Opera was popping up a problem dialog. not sure if that was entirely the problem, but if you'd like to see more of that discussion, it was in this thread: http://sahi.co.in/forums/viewtopic.php?id=3798