On 29 November 2011 05:04, Fabio Rodrigues <[email protected]> wrote:
> I have been using Jmeter to do some regression tests on the server-side.
>
> I’ve set up http proxy server and test plan (accordingly to apache web site
> step-by-step instructions), so that I can record all requests and play-back,
> all great so far.
>
> However, I have to keep the Jmeter GUI opened and click on File/Save to save
> the test plan manually, because it doesn’t flush to the test plan file
> automatically.
>
> Considering the non-gui JMeter parameter is only when playing a recorded test
> plan:
>
> + Is there anything I can do to make Jmeter flushes the requests to the test
> plan file straightaway whilst recording?
>
> There are 20 users testing the application with their browsers pointing to
> this Jmeter Proxy server, at the end of the day it wouldn’t be great, if for
> any reason, I can’t save those requests.

The JMeter Proxy server was originally designed for use with a single
browser (though of course that can make parallel requests).
As such, generally the person running the browser also runs the JMeter
Proxy and can save the test plan as needed.

Also, JMeter does not distinguish the source of the browser requests,
so the requests from different testers will be intermingled in the
test plan.

In general, this won't work on replay unless all the requests are
completely independent of each other.

In any event, the resulting test plan is likely to be very large and
difficult to understand and maintain.

I would suggest using some other kind of recording proxy - or the
server logs - to establish what needs to be tested and the relative
request frequencies, and then use that to generate and parameterise a
test plan.

> Regards,
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to