Handling Meta Refresh

[Guest alandraper]

I'm testing an e-commerce site which has a "wait page" between the checkout and complete pages.

 

It looks something like this

checkout.aspx-->wait.aspx-->wait.aspx-->wait.aspx-->complete.aspx

Wait.aspx uses an html meta refresh to continually reload the page until the user's session state changes (to ether indicate checkout complete, or checkout failed). At that point, there is a server-side redirect.

 

My problem is that WAPT doesn't seem to follow the refresh, so when running a test, WAPT never gets to the confirmation page. Is there any way around this? My only idea was to fake it with a fixed number of GET requests, but this won't really match actual user experience. And it seems to cause a server-side error if I guess the wrong number.

 

Any ideas?

 

[Guest angela]

I'm testing an e-commerce site which has a "wait page" between the checkout and complete pages.

 

It looks something like this

checkout.aspx-->wait.aspx-->wait.aspx-->wait.aspx-->complete.aspx

Wait.aspx uses an html meta refresh to continually reload the page until the user's session state changes (to ether indicate checkout complete, or checkout failed). At that point, there is a server-side redirect.

 

My problem is that WAPT doesn't seem to follow the refresh, so when running a test, WAPT never gets to the confirmation page. Is there any way around this? My only idea was to fake it with a fixed number of GET requests, but this won't really match actual user experience. And it seems to cause a server-side error if I guess the wrong number.

 

Any ideas?

 

Hi,

 

Unfortunately, in WAPT 5.0 it is not possible to compare variables, so please try to set User Think time for the time period required for the page to be refreshed.