Would it possible that in Firefox, the UI element corresponding to "EcisPlusUiQrInnie.expand" also got updated after the Ajax response came back? One way to verify this is to use the dump() method to generate all XPath locators for different UI objects including "EcisPlusUiQrInnie.expand", put a breakpoint on
click "EcisPlusUiQrInnie.expand" and try to find if the generated XPath could be found using DOM inspector/XPather plugin after the program stops at the above breakpoint, i.e., after the Ajax response comes back. Let us know what you find. If you use jQuery selector, it would be another story. Thanks, Jian On Tue, Aug 11, 2009 at 1:57 PM, Ben Groeneveld <[email protected]>wrote: > Reran the script using Firefox 3.0.13 and 3.5.2 on Fedora > 11 using your latest Tellurium TestNG reference project tellurium-0.6.0. On > this and similar ajax segments of the script: > times out waiting for ewlements expected to be present. The same script > works well on IE7 WindowsXP same Tellurium project. The best that I can > describe the behavior is "after an Ajax request subsequent searches for > elements already existing or newly added fail." For example, in the > following dsl: > click "EcisPlusUiCAV.Save" // Ajax > println "Testing - Pausing" > pause 10000 > > println "Testing - Verification In Quick Reference" > click "EcisPlusUiQrInnie.expand" // Ajax > println "Testing - Pausing" > pause 10000 > captureScreenshot "ExpandScreenShot.png" > def checkEmail = getText("EcisPlusUiQr.CustomerEmail") > > The .Save causes the second .expand to fail on a Selenium isElementPresent. > If I comment the .Save, then the .expand succeeds, but then the getText > fails on an isElementPresent. Yet the screenshot displays the element. It > would seem the Ajax requests are causing a side effect, not just related to > displaying previously non-existent content.. Hope that helps, BenG. > > > > On Mon, Aug 10, 2009 at 9:04 PM, Jian Fang <[email protected]>wrote: > >> I am also curious why it is not working for Firefox. If you increase the >> timeout threshold, the test still times out in Firefox? >> >> The new method waitForAjaxResponse will be added once Mikhail finishes the >> prototyping. >> >> Thanks, >> >> Jian >> >> On Mon, Aug 10, 2009 at 7:04 PM, Ben Groeneveld <[email protected]>wrote: >> >>> Works like a charm in IE on windows. We are curious - if you are using >>> Selenium underneath then why is it not working properly on Firefox? Is this >>> a Selenium restriction or . . . Development on unix would be preferable. >>> When do you anticipate availability in Firefox? Thanks, BenG. >>> >>> >>> On Mon, Aug 10, 2009 at 11:01 AM, Ben Groeneveld >>> <[email protected]>wrote: >>> >>>> That might be the issue - I am using Firefox on Fedora linux. I'll try >>>> it on Windows. >>>> >>>> >>>> On Mon, Aug 10, 2009 at 9:28 AM, Jian Fang <[email protected]>wrote: >>>> >>>>> waitForElementPresent is still a selenium call under the hood. Have you >>>>> seen the page updated before it timed out? Or >>>>> the 3000 is not long enough for the Ajax response? >>>>> >>>>> Mikhail is working on Ajax response and he made some progress on >>>>> Firefox, but is still working on IE. Mikhail, do >>>>> you have anything to add? >>>>> >>>>> Thanks, >>>>> >>>>> Jian >>>>> >>>>> >>>>> On Mon, Aug 10, 2009 at 11:56 AM, Ben Groeneveld < >>>>> [email protected]> wrote: >>>>> >>>>>> Our impression has been that with Tellurium we should be able to test >>>>>> for Ajax responses that produce page updates. Yet in our testing to >>>>>> date we >>>>>> are not able to test for or verify Ajax responses that update page >>>>>> regions. >>>>>> For example, the following DSL (below) that produces a page update will >>>>>> time >>>>>> out. Are there some specific settings that we should be using? Thanks! >>>>>> >>>>>> click "EcisPlusUiQrInnie.expand" >>>>>> waitForElementPresent("MailToo.mailto", 3000) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
