Hi, On 27.4.2011, at 12.44, kalyan reddy wrote:
> Hi, > Basically this would work only in case where ui being tested has elements > which are unique.(i.e no more than one Button, no more than one text element > etc) which could be extreme cases??. > No. You will have different ids for each button, each text element and so on. This is required by qml syntax as is. This way you will be able to identify the exact button, text, etc. using the id which is the same as in qml. Think if you have a form where you have text input for first name, last name and address. These can all be TextInput elements but they all need to have different id. The id usually describes the semantics of the element thus natural ids could be for example "fName", "lName", "address". Also you might have two buttons with ids like "Ok" and "Cancel". List item is the only case I think there is not so much use for this id but I think in all other cases it will be _very_ useful. Also with list items this could be useful if you have two different list items (for example for odd and even items) - then you would be able to use the id to differentiate between those kinds of list items. Petri > br, > kalyan > > On Wed, Apr 27, 2011 at 12:22 PM, Petri Kiiskinen > <[email protected]> wrote: > Hi, > > On 27.4.2011, at 12.11, kalyan reddy wrote: > >> Hi, >> >> Question related to the merger request: >> >> How can the id be unique and used for ui test automation??. For example I >> could have have three list items in a view and will it not fail to >> differentiate between them >> > > The id does not need to be unique. It will help to differentiate the Item > object from button object. If you need to differentiate between item objects > then you need to include also other attributes which combined will make the > unique identification possible (order, text, icon etc.). > > In many cases the id will be unique in the context of the application and > will help test automation a lot. Item object is probably one of the few cases > where this does not help too much? > > > Petri > >> thanks, >> kalyan >> >> On Wed, Apr 27, 2011 at 11:34 AM, Tang, Shaofeng <[email protected]> >> wrote: >> Actually, I just want to check if the merge request will be accepted or not. >> And sure, I will add the patch into my bug. >> >> -----Original Message----- >> From: Zhao, Juan J >> Sent: Wednesday, April 27, 2011 3:31 PM >> To: Tang, Shaofeng >> Cc: [email protected]; [email protected] >> Subject: Re: [MeeGo-dev] [Qt] When the patch for QML_ID will be available? >> >> On Wed, 2011-04-27 at 14:47 +0800, Tang, Shaofeng wrote: >> > Hello All, >> > >> > >> > >> > The merge request #2592 >> > >> > https://qt.gitorious.org/qt/qt/merge_requests/2592 >> > >> > has been committed for a while on Qt, and isn’t merged yet. >> > >> > And we also voted for it on Nokia’s forum. >> > >> > This patch is very important to our team for automatically testing QML >> > GUI application. >> File a bug to qt in qt's bugzilla? That's a matter of upstream. >> The problem won't stop you because you can file a bug in bugs.meego.com >> and add you solution there. Add add this patch to meego OBS devel:qml. >> > >> > >> > >> > I wonder if anyone knows when it will be accepted? >> > >> > Or if it has been rejected, please inform me. >> > >> > >> > >> > Thanks & Best Regards >> > >> > Shao-Feng >> > >> > >> >> >> -- >> *^_^* >> Many thanks & Best Regards >> SSD-OTC Meego Middleware & TV Team >> Zhao Juan >> _______________________________________________ >> MeeGo-dev mailing list >> [email protected] >> http://lists.meego.com/listinfo/meego-dev >> http://wiki.meego.com/Mailing_list_guidelines >> >> _______________________________________________ >> MeeGo-dev mailing list >> [email protected] >> http://lists.meego.com/listinfo/meego-dev >> http://wiki.meego.com/Mailing_list_guidelines > >
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
