Olivier ZORO-BI wrote: > Daniel Wagner wrote: > >> Hi Olivier, >> >> I strongly doubt it's a problem with the table widget itself. Either >> the qooxdoo Selenium extensions are buggy or it's somehow related to >> your test setup. >> >> Please check the following things: >> >> * Make sure you're using the same Simulator revision on all your >> machines. I've been working on the table interaction stuff recently >> and while it should only affect the way table *columns* are found, it >> doesn't hurt to make sure. >> >> * Check the return value of the getQxTableRows command. If you're >> using the Java language bindings from the Simulator, it's called >> qxTableGetRows. The row count should obviously be the same on all >> platforms. >> >> * Similarly, run getQxTableValue (qxTableGetValue in Java). >> >> * Run your qxTableClick command in Selenium IDE on both platforms and >> search the debug log output for "firstVisibleRow" and "final coords". >> >> >> I'll see if I can reproduce the problem in our test setup. >> >> >> Regards, >> Daniel >> >> Olivier ZORO-BI schrieb: >> >>> Hi, >>> >>> I Face a problem using qxTableClick(locator, "row, col, double=true") >>> on different platforms : Unix and Mac. >>> >>> The fact is that under Unix platform rows tables seems to start from >>> 1 and under Mac from 0. >>> So depending on the platform, tests fail. >>> >>> Is it a known problem by qooxdoo, is it a Selenium problem, ... ? >>> >>> Olivier ZORO-BI >>> >>> ------------------------------------------------------------------------------ >>> >>> >>> ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad >>> Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. >>> See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo >>> _______________________________________________ >>> qooxdoo-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> >>> >>> >> > Hi Daniel, > > After an investigation, It seems to be a problem in my code since the > problem appears only on one table : a table in a tabviewPage. > For the other used table (in a window) there is not any difference on > Linux and Mac platforms. > I still don't know why but I'll try to investigate with qxTableRows and > qxTableValue. > > Thanks for your help. > > Olivier > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > Hi again, I come again on this problem which I have investigated for a long time now. The qxTableClick(locator, "row, col, double=true") method seems to have a bug.
In facts, under Linux, to type in row 0 and col 0, I'm obliged to do qxTableClick(locator, "row=1, col=0, double=true"). But after editing the cell, I can get the good entered value with selenium.qxTableGetValue(locator, "row=0" , col=0" ); Could you test it? Under Mac It is never the same starting row or column, depending on the table instance. It's very amazing. Regards, Olivier ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
