I get the impression this user (no more 'he' for me) specifically wants to end up with JMeter sample objects in a test plan, maybe in order to modify them by hand.
-Mike On Wed, 2004-06-23 at 08:32, 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] -- Michael Stover <[EMAIL PROTECTED]> Apache Software Foundation --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
