Hi Jian I thought I still see a isElementPresent before every action . Let me check again
Regards Hari On Wed, May 20, 2009 at 6:38 PM, Jian Fang <[email protected]> wrote: > Yes, this is because we removed the isElementPresent() statement before > each action and thus have to rely > on Selenium core to throw exception when element is not found. We could > modify Selenium core to throw exception > with error code and capture it at the dispatcher tier, then wrap the > exception in Tellurium by the error code, but > this requires some work on Selenium core side. Are your tests dependent on > the exception type? If not, I will create > an issue for this, but would put it in low priority. > > Thanks, > > Jian > > > On Wed, May 20, 2009 at 3:49 AM, Harihara Vinayakaram <[email protected]>wrote: > >> Hi >> The Exception thrown when an element is not found is >> Screenshot for exception <<ERROR: Element >> //descendant-or-self::xforms:lab...@id="message"] not found>> is saved to >> file Screenshot1242805578993.png >> [testng] *com.thoughtworks.selenium.SeleniumException*: ERROR: Element >> //descendant-or-self::xforms:lab...@id="message"] not found >> >> I rememember there was a change made to say throw >> org.tellurium.exception.ElementNotPresentException >> >> Was this rolled back due to some reason ? >> >> Thanks >> >> Regards >> Hari >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
