On 19/02/2010, Brett Cave <[email protected]> wrote:
> Hi,
>
>  I have a load test strategy that consists of a number of tests run in 2
>  modes: soak and stress. Stress uses ramp-up over time, whereas soak uses a
>  constant number of threads. each test runs in both modes.
>
>  For example, I have the following tests:
>  homepageSoak
>  homepageStress
>  sitenavSoak
>  sitenavStress
>  specificpageSoak
>  specificpageStress
>
>  each test has 1 thread group, some HTTP Request Defaults, cookie manager and
>  HTTP Samplesr (no listeners). jmeter is start via command line (with -n) and
>  is used in distributed mode (-R server1,server2), with log file specified as
>  a parameter (-l testName.jtl). We then draw reports on each test in each
>  mode.
>
>  thread group configuration for all "soak" tests are the same, thread group
>  configuration for all "stress" tests are the same
>  sampler configuration for each test is the same across modes (i.e. homepage
>  tests both have same sampler / defaults configuration)
>
>  Is there a way to combine all the threadGroups into a single test plan and
>  have each threadgroup log results to a different file so we can draw the
>  reports we need from different files?

Yes, just add a Simple Data Writer to each thread group; use different
file names.

>  What would be the most effective (from
>  managing the test plans perspective) way to structure this?

I'm not entirely clear how the test plans differ.
If they are sufficiently similar that they can be parameterised, then
the same plan can be used for different purposes. E.g. thread count
and ramp-up could be defined using the __P() function, and the values
passed in on the command-line, e.g.

jmeter -n -t testplan.jmx -Jthreads=20 -ltestplan20.jtl -jtestplan20.log

etc.


>  thanks.
>
> brett
>

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

Reply via email to