OK, I updated both java client driver and server with the new 1.4 material.
Tests are still failing at the same place with the following error, no more blocking, so it is getting better : 19:41:29.688 INFO - Command request: qxEditTableCell[qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], type=rouge] on session 19:41:29.824 INFO - Got result: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] on session Few lines later in the log : com.thoughtworks.selenium.SeleniumException: ERROR: Hybrid locator couldn't find element using qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] at com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:97) at com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:91) at com.thoughtworks.selenium.QxSelenium.qxEditTableCell(QxSelenium.java:67) at novlog.uat.fwk.AbstractTest.editTableCell(AbstractTest.java:188) at [CUT] What is an hybrid locator ? What Hybrid mean ? Also, the locator look like "reworked" from qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"] to qxh=qx.ui.container.Composite/qx.ui.table.pane.Scroller/qx.ui.table.pane.Clipper/qx.ui.table.pane.FocusIndicator/child[0] and I don't think this rework is done in our code. Any idea ? Because we could have called the qxselenium with the wrong locator, I added a trace to reflect our call to the qxEditTableCell() method: [DBG] [AbstractTest] editTableCell(qxhv=*/[@classname="novlog.composer.ui.applicationexplorer.ApplicationExplorer"]/qx.ui.container.Composite/qx.ui.container.Composite/*/[@classname="novlog.fwk.ui.table.Table"], rouge) It sound like the internal structure of a qx1.4 table had changed, so the locator is wrong. What do you think about that idea ? About the bug you mentioned, it appears to be linked to TreeVirtual while we are using basic qx.ui.table.Table, could that be linked anyway ? Thanks for the help ! On 11 avr. 2011, at 18:00, Daniel Wagner wrote: > On 04/11/2011 04:51 PM, Jean-Baptiste BRIAUD -- Novlog wrote: >> Is there a new version of Selenium user extension for qooxdoo that come with >> qooxdoo 1.4 ? > Yes, it was moved to the framework for 1.4: > /component/simulator/tool/user-extensions/user-extensions.js > > The Simulator contrib (trunk) has an SVN external pointing to the > framework file. >> >> http://qooxdoo.org/contrib/project/simulator#selenium_user_extension_for_qooxdoo >> >> Test is failing taking 100% CPU on a table cell edition. >> No resize as far as I can see. > > So you can't reproduce this behavior by going through the test steps > manually? > > > Regards, > Daniel > > ------------------------------------------------------------------------------ > Xperia(TM) PLAY > It's a major breakthrough. An authentic gaming > smartphone on the nation's most reliable network. > And it wants your games. > http://p.sf.net/sfu/verizon-sfdev > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ Xperia(TM) PLAY It's a major breakthrough. An authentic gaming smartphone on the nation's most reliable network. And it wants your games. http://p.sf.net/sfu/verizon-sfdev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
