On 13/06/12 09:21 AM, Oscar Rieken wrote:
yeah its pretty hard to give an answer that might actually help without some code to look at.
I appreciate that. If this thread is otherwise unproductive, and my project leader can tolerate the greater than one hour added to the project that it will likely take to extract a minimal failing case, I'll give it another try ...
When the form is submitted what happens? do the fields become disabled? is there some sort of spinner to show that the forms is actually doing something?
No, there is no visible change to the page other than the web browser's own spinner to show that the page is loading.
why does the form take so long to do a post? Are users really going to wait longer than 30-60 seconds for the page to load?
I'm not seeing a 30s delay. watir-webdriver thinks it has a response immediately instead of blocking and waiting for the actual page to load.
I suggest watching what is happening in firebug's net tab and see what is running when you submit the form.
Did this already with Chrome's Developer tools. The post itself takes 1.87s. The balance of the time (up to 2.02s, the total time for loading the page) is consumed by loading various .css and .js files.
What OS are you on? what version of Watir-Webdriver? Because that might make a difference also.
Win XP SP3 + ruby 1.8.7 patchlevel 358 i386-mingw32 + watir-webdriver 0.6.1. Ben -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
