Catching errors as they happen: WebTest ValidateResponseUrl

In VS 2008, we added a new Validation Rule ValidateResponseUrl.

In VS 2005, a very common problem was that a page would redirect to the error page, but the web test engine did not automatically recognize this as an error. Then downstream in the playback another page would fail, usually with "hidden field blah not found in the context" error, as a side effect of the earlier error. Many times these errors would happen in a load test, but since it wasn't trapped as an error there was no error log for the page to figure out what was going on.

Many users hit this problem in 2005, and since the "side-effect" error was reported, but not the actual error, it was very confusing. This is problem is covered in both Web Test Authoring and Debugging Techniques, as well as Sean Lumley's great posts: Debugging Web Tests and Debugging Load Test Errors.

In order automatically catch redirects to the error page (which is exactly the case Sean documents in the Debugging Load Test Errors post), we 1) added the Expected Response URL property to web test requests, and 2) added test-level validation rules that apply to every request, and 3) automatically add the Response URL validation rule at the test level. Now if a page redirects to the error page, that page will fail. This is essential in a load test as it enables you to get the error details for that page. When this happens, it generates the error

The value of the ExpectedResponseUrl property 'http://webserver/errorpage.aspx" does not equal the actual response URL

Why does my web test pass if I run it, but fail if I run it in a load test?

The new rule can lead to unexpected failures in a load test.

In VS 2008, we also beefed up our vUser context in a load test. One thing the context now carries from iteration to iteration is the set of cookies for a user (thus emulating the browser cookie store). Let me take a typical example of how this can trip up your web test in a typical shopping cart type app. Record a web test as following:

Browse to an item and put it in your cart
Go to checkout
Checkout requires login, so app redirects to login
Login, which sets a cookie
Login redirects to checkout

When you run this in a load test, the vUser context will be carried from iteration to iteration, and the context contains any cookies set in a previous iteration. So the second iteration for the vUser will look like this:

Browse to an item and put it in your cart
Go to checkout
Checkout requires login, but now the user is already logged in (cookie is set) so app goes straight to checkout
The ValidateResponseUrl rule fails the web test because it is expecting to redirect to the login page

To fix this, you must explicitly log your user in during recording rather than counting on the redirect. If you only want the user to login once you can use the vUser Init and terminate functions in the load test test mix settings.


Comments (2)

  1. Uday Viswanath says:

    So, the case you explained is for Login and Logout scenario.

    But in my case, I am logged into my application using windows authentication directly. And I am getting the error "ExpectedResponseUrl  does not match with the Actual Response URL".

    Please suggest me how to overcome this.

Skip to main content