On 11/09/2007, Peter Laurens <[EMAIL PROTECTED]> wrote: > > ... > > The main reason is that, if you structure it correctly, then you > > have an > > evolution shell that you potentially apply to other projects. > > That's great advice, I think I'll take it :) > > I found this: http://minaret.biz/tips/jmeter.html > > Which looks like it includes lots of little bits to set up a nice > loop building jmx test plan files on the fly and running them sans- > GUI. Hopefully I will be able to hack it up and use it as a > foundation for my own thing.
BTW JMeter now contains an AccessLogSampler which can process server logs. Also test plans can use properties for most items, including thread count, ramp-up, loops and throughput timer. Further, the BeanShell server can be used to reset properties - see http://jakarta.apache.org/jmeter/usermanual/best-practices.html#beanshell_server for an example that may be relevant here. We used this approach for testing an application server to find out what sustained load it could support for various numbers of threads. > Thanks! > > - Peter > > --------------------------------------------------------------------- > 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]
