Follwing these advices

http://manual.qooxdoo.org/current/pages/development/simulator_locators.html

I've create a working locator
qxhv=*/qx.ui.toolbar.ToolBar/*/[@label="my-label"]

2011/9/19 Benjamin Dreux <[email protected]>:
> Hi Daniel,
>
> Following your advice i tryied this locator
>
> qxhv=*/qx.ui.toolbar.ToolBar/qx.ui.toolbar.Button
>
> This works fine.
>
> One step further, i want to select a specific toolbar button.
> My first idea was to use the label of the Button.
> So i used
> qxhv=*/qx.ui.toolbar.ToolBar/qx.ui.toolbar.Button[@label="my-label"]
>
>
> But this doesn't find the button.
> So i tryed to use the
> qxhv=*/qx.ui.toolbar.ToolBar/qx.ui.toolbar.Button[2]
> (is the meaning : second button ?)
>
> But it doesn't work neither.
>
> Does someone has advice for me ?
>
> 2011/9/19 Daniel Wagner <[email protected]>:
>> Hi Benjamin,
>>
>> you don't need to modify your application for testing if you use the qxh
>> and qxhv locators. They use an XPath-Style syntax to traverse the
>> application's widget hierarchy. The locator
>>
>> qxh=qx.ui.toolbar.Button
>>
>> is interpreted as "A *child* of the application root that is an instance
>> of qx.ui.toolbar.Button". But since the structure of your application is
>> probably more like
>>
>> qx.ui.root.Application
>>   qx.ui.container.Composite
>>     qx.ui.toolbar.ToolBar
>>       qx.ui.toolbar.Button
>>
>> You want a *descendant*, or in qxh lingo:
>>
>> qxh=*/qx.ui.toolbar.Button
>>
>> See the manual for an explanation of the qxh locator:
>>
>> http://manual.qooxdoo.org/current/pages/development/simulator_locators.html#qxh-locator-search-the-qooxdoo-widget-hierarchy
>>
>> The "qx" locator uses the userData property to find widgets. This
>> actually requires you to modify your application, so I don't recommend it.
>>
>>
>> Regards,
>> Daniel
>>
>> On 09/19/2011 04:53 PM, Benjamin Dreux wrote:
>>> Hi
>>>
>>> I'm trying to create a test using the Selenium IDE.
>>> After reading the documentation on the topic, I tryed to use the
>>> qooxdoo user extension.
>>>
>>> I found a version of the qooxdoo user extension in the  qooxdoo sdk
>>> (QOOXDOO_SDK/component/simulator/tool/user-extension/user-extension.js)
>>> I add this user extension into my selenium IDE.
>>>
>>> Then I rerun selenium, the extension is correctly loaded.
>>> I can use the qx* action.
>>> I've tryed to use the qx locator but without success.
>>>
>>> I've tryed qxh, qxvh with no more success.
>>>
>>> When using this target qx=qx.ui.toolbar.Button,
>>> I've got this error qx-locator: element not found for locator:
>>> qx-locator=qx.ui.toolbar.Button
>>>
>>> Do i need a special compilation of my app the be able to use the
>>> qooxdoo locator ?
>>> Is there some step I missing here ??
>>>
>>> Thanks for your help
>>>
>>>
>>
>> ------------------------------------------------------------------------------
>> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
>> Learn about the latest advances in developing for the
>> BlackBerry&reg; mobile platform with sessions, labs & more.
>> See new tools and technologies. Register for BlackBerry&reg; DevCon today!
>> http://p.sf.net/sfu/rim-devcon-copy1
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>
>
>
> --
> Benjamin Dreux
> Analyste-Programmeur
> Chaire de logiciel libre-Finance Social et solidaire
> UQAM
> Montréal
>



-- 
Benjamin Dreux
Analyste-Programmeur
Chaire de logiciel libre-Finance Social et solidaire
UQAM
Montréal

------------------------------------------------------------------------------
BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry&reg; mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry&reg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to