ok, I think I understand now. To paraphrase.

1. import in URL via some mechanism
2. manually change the threadgroup to simulate user session
3. run test


it sounds like you would like a better solution to 1 and 2 using some
sort of import. correct me if I'm wrong. the feature you are looking
for is something like this.

1. a file of URL's with multiple sets of request parameters
2. use a new plugin to import the file
3. the plugin generates a thread group with n HttpSamplers matching
exactly the same number of parameter sets in each line. Like say each
line does login, search and logout. the import would create three
HttpSamplers with the correct parameters in each.
4. run your test plan.

Is that an accurate interpretation?

peter


On Wed, 23 Jun 2004 15:54:53 +0200, Felix van Hove
<[EMAIL PROTECTED]> wrote:
> 
> Hello Peter,
> 
> thanks for the reply. I definitly should have a closer look at the access log
> sampler. Let me explain further, what I would like to get by an import feature.
> 
> If I get individual samplers by importing a list of (HTTP-) addresses, I can
> configure requests much more precisely. In my case I need to simulate half a
> dozen different users, who are subscribing to newsletters, login, logout,
> ordering products, registering etc. I need to url-rewrite nearly every request,
> iterating over productlists, address-lists, accounts etc. The import itself is
> only the first step in building the test plan for me.
> 
> If I am not focussing on server logfiles, I may also switch between different
> protocols, samplers, even server instances. I had the idea of stress testing a
> server by a combination of webservices- and user-requests; first I'd have to
> import SOAP requests and the usual HTTP requests, afterwards combining them to a
> complex test plan. Ok, I'm not sure, if such a scenario makes sense at all;-)
> 
> And last but not least a practical reason: As a customer, whishing someone to
> check my site, I would copy-paste URLs from the address line of my browser to a
> file. I actually got my linklist as a power point presentation :-)
> 
> Felix
> 
> 
> 
> Peter Lin wrote:
> > Mike recently made a lot of nice changes to AccessLogSampler.
> > Probably the easiest way is to write a parser that implements the
> > parser interface. then you can simply drop the jar file into /lib/
> > directory to use it with the AccessLogSampler.
> >
> > the original idea behind the accesslog sampler was to use production
> > access logs for simulating loads and running simulations.  This is
> > particularly useful if there's a bug that appears under very specific
> > situations. Say you discover a bug in a webapp, so you stress test it.
> > The bug doesn't appear with randomly generated requests.
> >
> > in cases like these from my own experience, it is the result of usage
> > patterns, which random requests can not reproduce.  the accesslog also
> > lets me compare one system to another and make apples-to-apples
> > comparison. well as close to apples-to-apples as possible.  if you
> > need help implementing the parser interface, just post a message and
> > I'll try to explain it to the best of my ability.
> >
> > peter
> >
> >
> > On Wed, 23 Jun 2004 12:53:08 +0200, Felix van Hove
> > <[EMAIL PROTECTED]> wrote:
> >
> >>I just started to prepare a jmeter add-on to import request lists,
> >>using each request parsed from the list to create a sampler suiting
> >>the protocol. But may be I'm overlooking an allready existing feature?
> >>(As far as I can see, the access log parser has a much more
> >>specialised - and different - idea.)
> >>
> >>Until now I'm focussing on linklists / clickstreams. The import parses
> >>a list of links (seperated by linefeeds) and creates a HTTP sampler
> >>(as a child of the current node) for each of them. It's taking care
> >>for preserving the protocol (which only can be HTTP and HTTPS until
> >>now), server name, port number, path and parameters (using
> >>HtmlParsingUtils.createUrlFromAnchor()).
> >>
> >>Background: I had to build a test plan by 79 requests, the clickstream
> >>file has 13792 characters, http parameters everywhere. Especially to
> >>paste parameters is extremly error-prone.
> >>
> >>I inserted this import function as a menu point in the file menu, -
> >>it's just opening a file-open dialog.
> >>
> >>Is there allready a better way for doing this?
> >>
> >>--
> >>easynet GmbH (http://www.de.easynet.net)
> >>Felix van Hove, system integration
> >>Harburger Schlossstrasse 1, D-21079 Hamburg
> >>fon: +49-40-77175-457, fax: +49-40-77175-498
> >># easynet is part of the easynet group plc (www.easynetgroup.net)
> >>
> >>---------------------------------------------------------------------
> >>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]
> >
> 
> --
> easynet GmbH (http://www.de.easynet.net)
> Felix van Hove, system integration
> Harburger Schlossstrasse 1, D-21079 Hamburg
> fon: +49-40-77175-457, fax: +49-40-77175-498
> # easynet is part of the easynet group plc (www.easynetgroup.net)
> 
> ---------------------------------------------------------------------
> 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