Give me some examples. On Wed, Aug 19, 2009 at 1:33 PM, satyadev <[email protected]> wrote:
> > How can I make sure that all UI modularised elements will identified > and located with out failure in with in whole page context? > > Did you got my Question ? > > > > On Aug 19, 10:17 pm, Jian Fang <[email protected]> wrote: > > Think about your html source structure. The UI modules present it and > match > > closely with it. If your html source does not have significant changes, > your > > UI modules > > will stay almost the same. > > > > How to define the UI modules is totally up to you. What really matters is > > that Tellurium > > generates the runtime locator based on the UI module when you code starts > to > > use > > that UI module. > > > > Thanks, > > > > Jian > > > > > > > > On Wed, Aug 19, 2009 at 1:05 PM, satyadev <[email protected]> wrote: > > > > > so we need to define/describe all 'ui elements' once with in page from > > > whole page context ? > > > and at same time we should able modularise all related ui elements ? > > > > > regards, > > > Satyadev > > > On Aug 19, 9:58 pm, satyadev <[email protected]> wrote: > > > > HI Jian, > > > > > > if it the case locator will change for each element. > > > > > > for example : I wrote testscripts for initial links like > News,MyCitrix > > > > test cases. > > > > Now locating stratgey is assume 'citrixpage.News' and > > > > 'citrixpage.MyCitrix'. > > > > Now I want write test cases for other links like 'DownLoads' and > > > > "about' Link. > > > > > > now my locating strategy for previouis elements changes as follows, > > > > > > 'citrixpage.TopMenu.News' and 'citrixpage.section.MyCitrix'. > > > > > > Don't it be pain to rewrite all our locator items once again. > > > > > > regards, > > > > Satyadev > > > > > > On Aug 19, 6:06 pm, John <[email protected]> wrote: > > > > > > > The UI module is generated by an algorithm. Of course, if you > > > > > have more elements, the algorithm will automatically adjust the UI > > > > > module > > > > > to cover all the elements with UI hierarchy. Note that, the > algorithm > > > > > will > > > > > group the UI elements into subgroups based on their location to > each > > > > > other in the > > > > > DOM. For example, the following link > > > > > > > UrlLink(uid: "a0", clocator: [tag: "a", text: "Log in", href: "/ > > > > > English/mycitrix/index.asp"]) > > > > > > > is adjusted into the following subgroup after you add more > elements, > > > > > > > Container(uid: "T4ddd", clocator: [tag: "div", id: "supnav"]){ > > > > > UrlLink(uid: "a0", clocator: [tag: "a", text: "Log > > > > > in", href: "/ > > > > > English/mycitrix/index.asp"]) > > > > > UrlLink(uid: "a3", clocator: [tag: "a", text: "My > > > > > Citrix", href: "/ > > > > > English/mycitrix/index.asp?ntref=hp_util_US"]) > > > > > > > This is the correct behaviour. > > > > > > > If you add more elements to the second UI module, you will see some > > > > > subgroups > > > > > will stay the same. > > > > > > > Thanks, > > > > > > > Jian > > > > > > > On Aug 19, 5:04 am, satyadev <[email protected]> wrote: > > > > > > > > Hi, > > > > > > > > I try to generate UI element description for two links like "Log > in" > > > > > > and "News" in websitewww.citrix.com > > > > > > > > steps 1) I generate for only two above links then UI description > as > > > > > > follows, > > > > > > > > Container(uid: "root", clocator: [tag: "div", id: "header"]){ > > > > > > UrlLink(uid: "a0", clocator: [tag: "a", text: "Log in", > href: > > > "/ > > > > > > English/mycitrix/index.asp"]) > > > > > > UrlLink(uid: "a1", clocator: [tag: "a", text: "News", > href: > > > "/lang/ > > > > > > English/news.asp?ntref=hp_nav_US"]) > > > > > > > > } > > > > > > > > steps2) I generate UI description for above two links and some > more > > > > > > links like ""Partners"" and "My Citrix" now UI element > description as > > > > > > follows, > > > > > > > > Container(uid: "root", clocator: [tag: "div", id: "header"]){ > > > > > > Container(uid: "T4dd", clocator: [tag: "div", class: > "qmmc", > > > id: > > > > > > "qm0"]){ > > > > > > UrlLink(uid: "a1", clocator: [tag: "a", text: > "News", > > > href: "/lang/ > > > > > > English/news.asp?ntref=hp_nav_US"]) > > > > > > UrlLink(uid: "a2", clocator: [tag: "a", text: > > > "Partners", href: "/ > > > > > > lang/English/partners.asp?ntref=hp_nav_US"]) > > > > > > } > > > > > > Container(uid: "T4ddd", clocator: [tag: "div", id: > > > "supnav"]){ > > > > > > UrlLink(uid: "a0", clocator: [tag: "a", text: > "Log > > > in", href: "/ > > > > > > English/mycitrix/index.asp"]) > > > > > > UrlLink(uid: "a3", clocator: [tag: "a", text: "My > > > Citrix", href: "/ > > > > > > English/mycitrix/index.asp?ntref=hp_util_US"]) > > > > > > } > > > > > > > > } > > > > > > > > why it is like this ? > > > > > > BY doing this way when ever I learn new element along with exist > > > > > > element my UI elements organization changes ? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "tellurium-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tellurium-users?hl=en -~----------~----~----~----~------~----~------~--~---
