Hi Olivier, you have to load the qooxdoo user extensions into Selenium IDE as described here:
http://qooxdoo.org/contrib/project/simulator#installing_in_selenium_ide Regards, Daniel Olivier ZORO-BI schrieb: > Daniel Wagner wrote: >> Hi Olivier, >> >> > [...@widgetid=window2]/[...@widgetid=tabview] >> >> This part of your locator seems strange to me since your Inspector >> screenshot shows the TabView within the second of two Composite >> containers. Try replacing this part with >> >> [...@widgetid=window2]/child[1]/[...@widgetid=tabview] >> >> I have no idea why [...@widgetid=tabview]/child[2] finds the >> tabview.Page. In my test case, this finds the SlideBar containing the >> tab buttons, while [...@widgetid=tabview]/child[1] finds the second page. >> >> One thing to keep in mind is that the child widgets of a tabview.Page >> aren't created until the page is activated for the first time. So if >> you're running automated tests, you'll probably have to click the >> second page's tab button first. >> >> If the above doesn't help, this is a good way to debug locators: >> 1) Load your application in Firefox with Selenium IDE >> 2) Set Selenium IDE's log level to "debug" >> 2) Manually click the second tab page to activate it >> 3) Enter the first part of your locator (qx...@widgetid=window2]) in >> Selenium IDE and click the "Find" button. >> 4) If a widget was found, a green border will flash on the DOM >> element. Make sure it's the one you wanted. If not, check Selenium >> IDE's log output to see what was found. Modify the step until it finds >> the correct widget, then add the next step and so on. >> >> I recreated part of your application's structure and used the method >> above to come up with the following locator for the first list item: >> >> qx...@widgetid=window2]/*/[...@widgetid=tabview]/child[1]/qx.ui.form.List/child[0] >> >> >> >> >> Regards, >> Daniel >> >> Olivier ZORO-BI schrieb: >>> Hi, >>> I want to use Selenium to do some User Acceptance Tests with my >>> Qooxdoo GUI. I have problems to rich some widgets. >>> I read the documentation and use a property widgetId that I put to >>> most of my widget, the child and the "*" locators. >>> >>> I used the Qooxdoo inspector to clearly have the hierarchy of my >>> application but I can't rich some widgets. >>> >>> You have joined a copy of the hierarchy of my application with >>> Qooxdoo Inspector. I would like to rich for instance the underlined >>> (blue) qx.ui.basic.label clicking on the qx.ui.form.ListItem. In >>> fact, can't rich any of the widgets in the Lists taviewPage although >>> I rich the tabviewPage with: >>> >>> selenium.qxClick("qx...@widgetid=window2]/[...@widgetid=tabview]/child[2]/child[1]"); >>> >>> command which I don't really understand because I would have put >>> ..../child[1]/child[1]. >>> >>> Have someone an idea? >>> >>> Thanks, >>> >>> Olivier ZORO-BI >>> >>> ------------------------------------------------------------------------ >>> >>> >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------------ >>> >>> >>> Download Intel® Parallel Studio Eval >>> Try the new software tools for yourself. Speed compiling, find bugs >>> proactively, and fine-tune applications for parallel performance. >>> See why Intel Parallel Studio got high marks during beta. >>> http://p.sf.net/sfu/intel-sw-dev >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> qooxdoo-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> > Hi Daniel, > I loaded my application with Selenium IDE. But do the Qooxdoo locators > work with it? It seems not with my application. I can reach my widgets > with div locators but not with qxh locators. > > cheers, > > Olivier. > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
