Inconsistent results with selenium RC

[santhosh venkat]

Dear All

I am running selenium RC. While running my regression the results are not consistent.

i.e, scripts which runs today are failing the other day. I am not sure why it is happening. Following are the exceptions that am getting often. I searched some forums and added the waitforpagetoload in many scripts. but still it is failing.  Kindly help what should i do to avoid this in the future

Exception 1 :

java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

Caused by: com.thoughtworks.selenium.SeleniumException: ERROR: Command execution failure. Please search the forum at http://clearspace.openqa.orgfor error details from the log window.  The error message is: Permission denied

at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97)

at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91)

at com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:167)

Exception 2 :

java.lang.reflect.InvocationTargetException

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

        at java.lang.reflect.Method.invoke(Unknown Source)

       

Caused by: com.thoughtworks.selenium.SeleniumException: ERROR: Command execution failure. Please search the forum at http://clearspace.openqa.org for error details from the log window.  The error message is: Unspecified error.

        at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97)

        at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91)

        at com.thoughtworks.selenium.DefaultSelenium.click(DefaultSelenium.java:167)

Exception 3 :

java.lang.reflect.InvocationTargetException

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

        at java.lang.reflect.Method.invoke(Unknown Source)

        

Caused by: com.thoughtworks.selenium.SeleniumException: ERROR: Current window or frame is closed!

        at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97)

        at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91)

        at com.thoughtworks.selenium.DefaultSelenium.open(DefaultSelenium.java:335)

Thanks

Santhosh

[santhosh venkat]

Hi

Is there an response for the below question ?

Santhosh

[Mark Collin]

At a guess it looks like the browser process has been killed whilst Selenium is trying to run tests and as a result it’s unable to execute commands on the browser. 

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To post to this group, send email to seleniu...@googlegroups.com.
To unsubscribe from this group, send email to selenium-user...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/selenium-users?hl=en.

-- This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error please notify postm...@ardescosolutions.com

[santhosh venkat]

No, the browser is still alive... Since i did not fine any answer from anyone. I hope it might be a bug with selenium or the selenium could not able to run the regression ?