Hi, I don't see why it should make such a difference. If you're able to reproduce the problem, please open an issue with the necessary information.
Cheers, Marc. -- Blog: http://mguillem.wordpress.com Hesteric Roman - Together SK wrote: > Hi Marc, > > We are using previousresponse in macro-step "clickAllLinks" to > check if all our links in page "work" properly ... > > Macro looks like: > > . > . > . > > <repeat > xpath="//a[contains(@href,'ID=')][not(contains(@href,'ID=&'))][not(c > ontains(img/@src,'fk.gif'))] bla.. bla ... " counterName="curLink"> > <storeXPath xpath="$curLink" property="uri" /> > <invoke description="Click next link" url="#{uri}"/> > <not description="the word 'wurde in der Zwischenzeit' should > not appear in the page"> > <verifyText description="search for the problem, case > insensitiv" text="wurde in der Zwischenzeit" regex="false"/> > </not> > <previousresponse/> > </repeat> > > . > . > . > > After clicking and checking result, we use previousresponse to > navigate <Back> to root page and so on - and that is problem using > autorefresh, because in both cases we get various results because of > redirect based on response body, IMHO. > > > Roman. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Marc Guillemot > Sent: Thursday, April 10, 2008 11:50 AM > To: [email protected] > Subject: Re: [Webtest] autorefresh vs. previousresponse > > Hi, > > at which place do you use previousResponse? Which page do you get in > both cases? > > Cheers, > Marc. _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
