|
Re: Robot Exception: Window activation failed [message #987043 is a reply to message #986789] |
Fri, 23 November 2012 07:32 |
|
Hi
well, we tried Xvfb a few years ago for our nightly test. We never got it to run reliable. There have been unexplained hangups, problem with keyboard input, totally different AUT behaviour and some others. We finally gave up and switched to VMware ESXi.
So you have been warned! Since there might have been improvements in Xvfb you can try but have to look into the following:
Make sure the keyboard type is well defined.
The standard window activation method is "Click in titlebar". For that to work there has to be a titlebar . You have to start a window manager for the Xvfb. That is probably a good idea in itself since a lot of programs act really strange without a WM.
If you can't (or don't want to) run a WM change the default activation method to something different. Which is best is depending on your AUT.
HTH
Achim
|
|
|
|
Re: Robot Exception: Window activation failed [message #1580720 is a reply to message #987343] |
Fri, 23 January 2015 17:25 |
|
I am encountering a similar situation...I am able to successfully run my test suite via eclipse or command line using the test executor. But when I have a Hudson job start the job on a slave machine and the AUTAgent successfully starts and is able to and connect to the AUT. However, the test step to perform an InitTestExecutionCommand for an executeExternalCommand results in an error to activate the AUT due to RobotException: Window activation failed. The test report is able to take a screenshot and several test steps were reported as executing successfully prior to this failure. Only the step to executeExternalCommand is encountering this error. I am running Jubula_8.0.00170 on RHEL_5. The command in the executeExternalCommand is an alias to execute a shell script.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03633 seconds