I've yet to find a dependable way to handle redirects. Suppose I jump directly to a url (using urlConnect) we'll call Page A, which immediately redirects to Page B. After connecting to Page A, my test continues and looks for an element on Page B by calling waitForElementPresent. Tellurium hangs indefinitely here, presumably because it's searching for the element on Page A. Oddly, it never times out after the specified 10 seconds.
One solution I was examining: after connecting to Page A, I can examine the url (using the getLocation method) until it matches something that looks like Page B, at which point I can proceed. getLocation seems to hang indefinitely as well. Any general advice for tackling this problem? Thanks! - Josh -- 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.
