Hi there,
as there seems to be some qooxdoo-related selenium knowledge available
here, I hope someone might give some useful hints.
Currently I'm trying to write some Selenium tests with Selenium IDE for a
RAP-application and I have my first testcases working (thanks to the
selenium-qooxdoo-extensions).
The problem is - by 'working' I mean - it's only working when running the
script very slow or inserting 'pause' - steps.
I want to replace this arbitrary 'pause'-steps with robust waiting.
Let's just explain my problems with a very simple use-case:
'starting a RAP-Application, and then clicking on just one button'
Behind the scenes the following is happening:
1) URL is entered into the browser, RAP-HTML-Page ist loaded with default
qx-library-Script, Main-RAP-Class is started.
2) MainClass creates a first request to the serverside (using
qx.io.remote.Request), the serverside sends back a qooxdoo script with the
initial GUI
3a) this qooxdoo-script is evaluated and
3b) the initial widgets are created.
4) I want to click a button.
The first problem of course is waiting for the remote request to finish
(step2). Actually this is not too hard, because in RAP there is a
qx-singleton (org.eclipse.swt.Request) which keeps a counter of all
running request. So I just have to wait for this counter to be 0 again.
I also have to wait until the qooxdoo-script is evaluated (3a), but I have
luck - the request counter is only set back after the script from the
server was evaluated !
My Selenium-Script thus looks like this:
open
rapApp/start
waitForCondition
var
tmp=selenium.browserbot.getCurrentWindow();tmp.wrappedJSObject.org.eclipse.swt.WidgetManager.$$instance
10000
waitForCondition
var
tmp=selenium.browserbot.getCurrentWindow();tmp.wrappedJSObject.org.eclipse.swt.Request.$$instance._runningRequestCount==0
10000
qxClick
//[EMAIL PROTECTED]"images//16x16/calendar.png"]
(The first 'waitForCondition' checks for something - creating another
RAP-singleton - that happens in step 3a, just to make sure that we are
really within step 3a)
Nevertheless ... even with those two waits, 'qxClick' is still too fast
and not finding the image without a prior 'pause'.
Could it be that qooxdoos widget queues are interfering ?
I'm quite sure, that with the script above I correctly wait for the
qx-script to be evaluated (3a) - but ... isn't qooxdoo deferring/delaying
all things that manipulate the browser DOM (i.e.
qx.ui.core.Widget._globalWidgetQueue in qooxdoo 0.7.3) ?
I think that even in non-RAP applications these queue's could make testing
complicated, if for instance a click on a button opens a dialog ?
Would it make sense to provide a 'waitForQxIdle()' function, that somehow
checks, that all queues are empty ?
How are other people making their selenium-tests wait robustly ?
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
