In this section, you will learn how to create advanced Test Plans to test a Web site.

• 6.1 Handling User Sessions With URL Rewriting

For an example of a basic Test Plan, see Building a Web Test Plan.

If your web application uses URL rewriting rather than cookies to save session information, then you'll need to do a bit of extra work to test your site.

To respond correctly to URL rewriting, JMeter needs to parse the HTML received from the server and retrieve the unique session ID. To do this, put all your requests inside a , with an attached. Then, include the session ID as an additional parameter with each , with ".*" as the value.

Download this example. In Figure 1 is shown a test plan using URL rewriting. Note that all HTTP Requests are contained within the . The also has an attached to it.

It would be possible to use other Logic Controllers within the without affecting the Modification Manager.

Figure 1 - Test Tree

In Figure 2, we see the "Send Parameters with Request" section of one of the objects. It shows, in addition to the login information, the SESSION_ID parameter, with a value of ".*", which is a regular expression that will match any string. Your application will have its own unique name for this parameter, which you will have to put in place of "SESSION_ID".

Figure 2 - Request parameters

The lets you customize what information JMeter sends in the HTTP request header. This header includes properties like "User-Agent", "Pragma", "Referer", etc.

The , like the , should probably be added at the Thread Group level, unless for some reason you wish to specify different headers for the different objects in your test.