BTW, are you using jQuery selector with the caching option? If yes, try to disable the cache first. If still not working, go back to use XPath for the time being.
We added logging capability in the custom selenium core, but removed it because of the degradation of the test speed. I will add the logging back so that you can enable and disable the logging function through API, i.e., in DslContext. In this way, at least we should know where the problem is. Thanks, Jian On Wed, Aug 12, 2009 at 9:15 PM, John <[email protected]> wrote: > > Would it be possible for you to pack your project to only include that > page's html source > and the corresponding test cases. Then send them to my email address. > I can use the MockHttpServer > to debug your code. > > Thanks, > > Jian > > On Aug 12, 6:40 pm, Ben Groeneveld <[email protected]> wrote: > > We looked at this in Windows Firefox also with the same results. In > debug > > at breakpoint after Ajax requests an examination with Firebug shows the > tag > > is there. But the tag is not found by our DSL or TestNG codes. We did > not > > verify this with teJQuery just Firebug. > > > > If we write a SeleneseTestcase and perform the same test - > isElementPresent > > - the id is found. So it would seem to be some issue with Tellurium > > processing. > > > > Not sure how to proceed. It is nice that it works in IE, but all of our > > continuous integration is on a Redhat server. Hope that helps, BenG. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
