From: Dave S. <dav...@ca...> - 2004-04-01 15:10:29
|
Yah .. in my case it is the first page that they enter so we are trying to test some basic navigation. For me there are two cases ... 1) Just ignore the refresh. 2) A callback that would allow me to insert data into the database then execute the refresh. It would seem that the a callback boolean executeRefresh(int time); Would be in order .. If it returns false then do not refresh otherwise refresh. I would say the default case would be to not refresh because the only test case I can think of would involve manipulating data before the page is refreshed. This would require notification of the refresh attempt. On Thu, 2004-04-01 at 09:58, Mike Bowler wrote: > Dave Smith wrote: > > > Well I can tell you there is a meta tag for refresh but it is 60 secs. > > It looks like this ... > > <meta HTTP-EQUIV="REFRESH" > > CONTENT="60;URL=https://192.168.1.2:8443/aci/FindShipmentAction.do"/> > > Looks like you are ignoring the time in seconds ... > > Yes, HtmlUnit is ignoring the time and is doing an immediate refresh. > I'd assumed, incorrectly it seems, that nobody cared about testing the > intermediate pages and that going straight for the refresh would work > for everyone. > > This will need to be revisited. I suspect that waiting for the full > time isn't really what's desired either as that will cause the tests to > take much longer to run. Possibly a callback mechanism so that the > tests can be notified that they are viewing a page that will be refreshed. > > Suggestions are always welcome. -- Dave Smith CANdata Systems Ltd 416-493-9020 |