On 21/03/07, Alf Høgemark <[EMAIL PROTECTED]> wrote:
HiI have used Jmeter to test Spring Webflow applications. I did not record the test via the proxy server, but built it from hand. Here are my suggestions. I use a cookie manager. I add a Post Processor->"Regular Expression Extractor" as a child to the first HTTP request which starts the "webflow". That "regular expr. extractor" looks like this : Reference name : flowId Regular Expression : name="_flowExecutionId" value="(.+?)" Template : $1$ Match no : 0 Default value : dummy (I use this just see if I'm not able to extract the value Then on all subsequent HTTP requests for the same "flow", I have a request parameter : with name _flowExecutionId and value ${flowId} This means that when the flow starts, you will pick up the dynamically generated flowId, and it will be used in all subsequent requests in the same flow.
I think this is effectively what the HTTP Url rewriting modifier should do ... but the problem is that the Proxy made some mistakes, see below.
This means you will have to do a little bit of manual work, after capturing the the test plan via the proxy server. I also think you should remove the "?_flowExecutionKey=_c1E11178E-485F-3913-98BA-86E17A09FA3D_kE977CB0B-47FE-3319-A688-FE4F4FFFCE28" from the "Path" of each request. You should not have the parameter both in the URL and as a request parameter in the table in the HTTP Request. I think I'll look into improving the HTTP Proxy Server, so that it removes the parameter from the URL, but for now, you have to do it by hand.
I've now had a look at the test plan, and it looks as though the proxy correctly extracts the parameters from the request, but where there is more than 1 parameter it seems to leave the _flowExecutionKey in the path - as well as generating a parameter for it - which is clearly wrong. If that was fixed, the plan would have been better, but still not ideal, because it would still have the _flowExecutionKey parameter on each sample. So it would be useful if the Proxy could be told not to save the values of certain parameters in the generated test plan - i.e. the parameters which we know need to be generated at run-time. [It would need to remove these after the sample had been used to return the data to the browser, of course] S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
