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: Permission denied.
Although my test runs perfectly in Firefox and also in IE when running in Debug mode, in IE in Run mode it fails with the error message above. selenium.waitForPageToLoad("20000"); doesn't seem to be a solution.
Any other ideas?
What command is failing with the Permission Denied? It may be when trying to access something that doesn't exist yet. I would recommend using the waitForCondition command to ensure the target element is present/visible before attempting to interact with it.
I used Thread.currentThread().sleep(1000); after the action that requires time to reload parts of the page. It seems to work, but not in all of the cases.
Related
I'm experiencing a problem that I could not find a solution for yet.
I use Test Complete to automate some GUI related scenarios for an app. I developed some scripts that were working at some point in the past. After a few months I got back and tried to run one of the scripts. The script failed with the following error while it was executing a ClickCell operation on a grid object.
An error occurred.
Possible reasons:
1. The application stopped responding.
2. The application was compiled incorrectly (see the Open Applications topic in the help system).
3. An error occurred in TestComplete.
Technical information:
379 0x80070057 (The parameter is incorrect.) .
Tested object:
...
I executed the same script on another machine with another Test Complete installation and it worked. So I guess it's not the target app that is the problem.
I checked solutions on the web for this issue, but nothing worked. I cleaned up the temp files in all the locations I could find in this answer. The behavior was the same.
So I guess it might be something related with the Test Complete installation. I tried reinstalling it a few times, but it didn't do the trick.
I then used Dependency Walker (as suggested somewhere on the web) on testcomplete.exe and found that there are some dlls that are missing from the Bin directory of Test Complete. Could they generate this error? If yes, how can I get them? As I said, I already re-installed the app a few times.
Did anyone bump into this while working with Test Complete? Is there any .net temp location that I should clean?
This test works locally, but when run from the Play test runner on our aws ci instance, I get the following permissions error in Firefox: Permission denied for HOST to get property Location.href and then Command execution error.
In Chrome, the remote message is different, but I sense the same underlying reason. Object <> has no method 'getCurrentWindow'.
Is it this issue? http://code.google.com/p/selenium/issues/detail?id=703
you are using the Play standard test runner from a remote location, which is the source of the issue (as far as I know).
Try to use play auto-test as described here to run the tests.
I get this error when running a number of tests in seleniums Bromine, The selenium RC version 1.0.2 outputs this:
WARN - GET /selenium-server/driver/?cmd=testComplete&1=&2=&sessionId=1274d41621c64fc08c1e7ea0a58f260b HTTP/1.0 java.lang.IllegalStateException: unexpected command json={command:"open",target:"/Library/Security/Login.aspx?ReturnUrl=%2fIndex.aspx",value:""} in place before new command selectWindow could be added at org.openqa.selenium.server.CommandQueue.doCommandWithoutWaitingForARe
sponse(CommandQueue.java:121)
Any ideas
Recently I had to track this problem on our testing environment and it appears, that the reason was Firefox crashing. If this error follows two 'Command timed out' exceptions, then your browser probably crashed or hanged.
Upon inspection of code of Selenium RC I realized that 'Unexpected command' error appears when there is an overflow in command queue. This can be caused by lack of responses from the browser, so if browser crashes, you end up receiving this error.
Check your dmesg logs (or some other logs, if not under Linux) to see, if there is anything suspicious. In my case there were entries like this:
plugin-containe[30867]: segfault at 0 ip 00007f07a6ff503d sp 00007f079d593260 error 4 in libxul.so[7f07a6265000+146f000]
libxul.so and plugin-container are modules of Firefox. Upgrading it to newer version helped in my case.
I'm also seeing this IllegalStateException, much too frequently. Its occurrence seems random, as if something in Selenium isn't synchronized properly. I have seen it several times in connection with a TestNG Listener that calls selenium to do a screen capture, but again, it's unpredictable.
I am starting to develop a new air/html/ajax application today and for some reason my trace() output is not being printed to the console window anymore. Plus, I am also not getting any error messages printed for syntax errors or runtime errors. I tried this on a different machine and there was no problem, so it must have been something wrong with this particular machine. I was thinking it had to do with me using the flex 3 sdk, but removing that from my path variable did not help, neither did reinstalling the air sdk. If anyone has encountered this before, help would be greatly appreciated.
This is not specific to the debugger player. The availability of trace statements in the console from ADL is dependent on whether or not any one of the following settings are turned on in your mm.cfg file:
ErrorReportingEnable
TraceOutputFileEnable
Either one of those will block trace output in the console window - stderr I believe - and instead (in the case of TraceOutputFileEnable) redirect it to a log file.
More information about mm.cfg is available here.
I figured it out. It is because I installed the flash debug player. Now the error messages all go the the log file where the debug player writes to.
We are randomly seeing this error during long executions of our system. The error is caught by our alarm system, and we successfully retry, and continue running the system. The only hits we found on Google seem to mention corrupt installations. We do not think this is the case here, since our systems are running, get the error, and can continue running.
Register the .dll file again from a command window by using the below command:
regsvr32 C:\WINDOWS\system32\msvbvm60.dll