Thanks Jarmo Pertman and Dave McNulla I will try yours suggestions. Yes this application is user-unfriendly.. I hope development make more friendly on next version.
On 30 Gruo, 00:04, Dave McNulla <[email protected]> wrote: > That sounds really ugly from a usability standpoint. Maybe it could be > implemented as a wizard, get input, click Next, get next set of > choices, select one, click next, etc. The hard part there is getting > people to scrap a bad design - they love their output even if it's > ugly. You'll have to find an effective way to get them to scrap it. > > Other possibilities (not sure which will work): > * wait until clicking on the next field does not produce a popup > (sounds like it wouldn't work) > * look for an attribute change in the next field, wait until that > happens > > Good luck, > > Dave > > On Dec 28, 7:06 am, xeranas <[email protected]> wrote: > > > > > > > > > If user too quick click next input (e.g. field 'B') while request for > > field 'A' isn't finished warning pop-up shows up. After it close pop- > > up and request still isn't finished user can fill other inputs (field > > B, field C and so on) no more pop-up shows up (it shows only once via > > request) BUT after request field 'A' is was finished all fields which > > was filled until field 'A' response are cleared (deleted values). > > "what is the essential point of that request or these requests" > > These request sent data to db or other services and waiting response. > > The response data needed for collecting future data. > > > Application sent and retrieve data on almost every input. User are > > forced wait till get response (all additional inputs will be cleared > > if user enters). These request are visible on browser status bar, but > > it looks like Watir don't see them :( > > > On 28 Gruo, 14:14, Jarmo Pertman <[email protected]> wrote: > > > > So what happens if the request is made? How do you as a user use that > > > page and what value will you get if that request is made? In another > > > way - what is the essential point of that request or these requests? > > > Try to think in these terms what could you set as your condition. > > > > If there isn't any point, then do you even have to care about these > > > requests? Why? > > > > Jarmo Pertman > > > ----- > > > IT does really matter -http://www.itreallymatters.net > > > > On Dec 27, 5:03 pm, xeranas <[email protected]> wrote: > > > > > Hi, i'm new with Watir and I need help with situation below.. > > > > > I'm trying create tests for web application. The problem is that > > > > almost every input send request to main server when input was > > > > triggered. After request response page content have not changed. > > > > > The only one field request can exist at time on my web application. > > > > Other inputs must wait until previous field request are finished. > > > > > So i'm stuck. ie.wait not help, ie.wait_until with .exit? also not > > > > help (page content haven't change after response). The only thing help > > > > is sleep. But i don't want add sleep on every input X sec (response > > > > sometime get almost instant but sometime need wait more than 1 min..) > > > > > I need be sure that no requests running at the moment before next test > > > > step. Maybe I misread function which help with my problem.. > > > > > Any help is much appreciated -- 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]
