I moved the waitForPageToLoad to no bundle list, please try the following jar and see what you get.
http://maven.kungfuters.org/content/repositories/snapshots/org/telluriumsource/tellurium-core/0.7.0-SNAPSHOT/tellurium-core-0.7.0-20100322.171928-110.jar Thanks, Jian On Mon, Mar 22, 2010 at 1:03 PM, Jian Fang <[email protected]> wrote: > Ok, we can fall back to change waitForPageToLoad as a native selenium call > instead of putting it to a bundle > and to see if the problem goes away. > > Thanks, > > Jian > > > > On Mon, Mar 22, 2010 at 12:57 PM, Jonathan Share <[email protected]>wrote: > >> On 5 February 2010 22:15, Jian Fang <[email protected]> wrote: >> > Hi, >> > >> >> * Snip * >> >> > >> > The waitForPageToLoad is not really the cause of your problem. The root >> > cause is the >> > click() method in Tellurium API did not work for element with a href >> > attribute. >> >> * Snip * >> >> > Please keep testing the click method on more >> > complicated >> > UI elements. >> > >> >> I've finally been allocated some time to start looking at out >> tellurium tests again and my first priority is getting them running on >> the latest snapshots. I seem to be having a similar problem to the one >> described above with click events on Button elements that trigger >> javascript. "My" markup looks similar to the following; >> >> <form onsubmit="showSpinner();" name="form_name" method="post" >> action="/doSearch"> >> <button type="button" onclick="document.form_name.submit(); >> showSpinner();">Search</button> >> </form> >> >> And I have modelled the button as a SubmitButton (tried also with a >> Button) as follows; >> >> ui.Form(uid: "common", clocator: [name: "form_name"]) { >> SubmitButton(uid: "search", clocator: [tag: "button"]) >> } >> >> When clicking on the button and monitoring network traffic with >> firebug I see that the form post takes ~800ms to complete and answers >> with a 302 reply to the results. However, with the following test >> script; >> >> println "######################## ${new Date().getTime()}" >> click "common.search" >> println "######################## ${new Date().getTime()}" >> waitForPageToLoad 10000 >> println "######################## ${new Date().getTime()}" >> waitForElementPresent 'resultForm', 10000 // Potential workaround >> println "######################## ${new Date().getTime()}" >> >> Which produces the following output; >> >> ######################## 1269276571516 >> ######################## 1269276571641 >> ######################## 1269276571688 >> ######################## 1269276572844 >> >> This clearly shows that waitForPageToLoad is returning too soon in >> this case. Am I wrong to use waitForPageToLoad in the case where a >> form is submitted via javascript triggered from onClick in this >> manner? This has worked in an earlier 0.7.0 snapshot. >> >> Thanks in advance, >> >> Jonathan >> >> -- >> 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]<tellurium-users%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/tellurium-users?hl=en. >> >> > -- 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.
