Another possibility is that the element you defined is not unique. You could try to use
diagnose(uid) http://code.google.com/p/aost/wiki/UserGuide070TelluriumAdvancedTopics#Tellurium_Powerful_Utility:_Diagnose to check how many matches at run time. Thanks, Jian On Fri, Feb 4, 2011 at 5:07 AM, ghanshyam baheti <[email protected]>wrote: > Hi Jian, > > Thanks lot for reply. > I done changes as suggested approach like :- using 'waitForPageToLoad(90 > 0000)' and then waitForElementPresent("Uid", 900000) before doing > operation on the element. > > In this case also where 30 min's given to load page and element *few times > unable to find the element.* I can see the element on page and verified > using firebug. > > *Still not getting UID. Please suggest what may be the reason?* > > > *Thanks,* > Ghanshyam Baheti > > > > > On Thu, Feb 3, 2011 at 8:25 PM, Jian Fang <[email protected]>wrote: > >> Please see my reply inline. >> >> Thanks, >> >> Jian >> >> On Thu, Feb 3, 2011 at 8:06 AM, ghanshyam baheti >> <[email protected]>wrote: >> >>> Hi All, >>> >>> I am getting some inconsistent behavoiur while running tellurium >>> testcases. Please help me or suggest the appropriate approach of >>> implementation in resolving below issue's or query. >>> >>> 1. What is exact difference between 'waitForPageToLoad(30000)' and >>> 'pause 30000' selunium methods. >>> *I mean Is 'waitForPageToLoad' also takes pause for 30000 ms or is it >>> waiting till all components are loaded on page? * >>> my observation is 'waitForPageToLoad' takes pause of max time that we >>> provided and does not resume immediatly once page is loaded. >>> >> >> pause is thread sleep. waitForPageToLoad is to setup a timeout value and >> the call may return at any time. Usually you should use waitForPageToLoad. >> >>> >>> 2. *How does tellurium engine identifies if element present using >>> 'waitForElementPresent' ?* Does it operates after page is fully loaded >>> or while page is loading? >>> >>> I am using below function where I am checking element presense using >>> 'waitForElementPresent' and then doing operation on it. Still few times >>> getting error of that 'element not find' though I can see element on page. >>> *Why this inConsistentcy is coming, Can you suggest the right approach >>> if any?* >>> ** >>> *private* *void* *enterFieldData*(hMap){ >>> hMap.*each*() { key, value -> >>> * println* "${key} == ${value}" >>> String elementName = "${key}" >>> String elementValue= "${value}" >>> waitForElementPresent("AddAssetForm." >>> +elementName,intElementLoadTime) >>> * if*(elementName.toString().equals("AssetName") || >>> elementName.toString().equals("Biller") >>> || elementName.toString().equals("Description") ){ >>> type "AddAssetForm."+elementName,elementValue.toString().trim() >>> pause 1000 >>> }};} >>> >> >> >> waitForElementPresent in Tellurium engine is delegated to Selenium call. >> >> In your test case, you should make sure the page is fully loaded, for >> example, use waitForPageToLoad(). >> >> >> >> > > > -- > Thanks, > Ghanshyam Baheti. > > I am a little pencil in the hand of a writing God who is sending a love > letter to the world. > ------------------------------------------------------------------- > -- 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.
