Hi
this is what I might try
Option A
Thread group 1 ${__property(threadCount)} number of thread, Loop
${__property(loopCount)} times
   -- Can have some random behavior here like interleave, throughput
     Each Webservice
      Each Soap Request
CSV Data Set config (60 records worth of data)

Ant script
  Call Jmeter with different properties
    <jmeter
        jmeterhome=".."
        testplan="${run.test.plan}"

resultlog="${report.dir}/${run.test.report}-${run.env}-${DSTAMP}${TSTAMP}.jtl">
        <property name="jmeter.save.saveservice.output_format" value="xml"/>
        <property name="threadCount" value="1" />
        <property name="loopCount" value="60" />
    </jmeter>

    <jmeter
        jmeterhome=".."
        testplan="${run.test.plan}"

resultlog="${report.dir}/${run.test.report}-${run.env}-${DSTAMP}${TSTAMP}.jtl">
        <property name="jmeter.save.saveservice.output_format" value="xml"/>
        <property name="threadCount" value="5" />
        <property name="loopCount" value="12" />
    </jmeter>

Option B
Common Thread Group (Disabled , needed only to define the common tests)
   Simple Controller --> Under here you could use different controllers if
you wanted to randomize the requests (Interleave, Throughput etc)
     Each Webservice
      Each Soap Request
     User Parameters or CSV data set config (this is the bit im not sure
will work , if it doesnt then Id use a CSV data set config and repeat the
configuration for each thread group but the data isn't duplicated so i think
thats ok)

Thread group 1 1 thread, Loop 60 times
   Module Controller --> Common Group --> Simple Controller


Thread group 2 5 thread, Loop 12 times
   Module Controller --> Common Group --> Simple Controller

Configure Thread Groups to run serially



regards
deepak


On Wed, Jul 29, 2009 at 2:19 AM, Erik Drolshammer <[email protected]> wrote:

> Hello!
> I'm pretty new to JMeter, and I'm struggling with how to parameterize it
> properly.
>
> My use case:
>
> for each Webservice
>  for each SOAP request
>    run 1 user, 60 loops   (60 samples)
>    run 5 users, 12 loops  (60 samples)
>    run 10 users. 6 loops  (60 samples)
>    run 15 users, 4 loops  (60 samples)
>    run 20 users, 3 loops  (60 samples)
>
>
> I am initially trying to do one of the soap xml requests at a time, but it
> would probably be better to have some sort of mix using different requests.
> Either will do.
>
> Can anyone advice me on how to set this up?
> Or point me to the relevant concepts in the documentation?
>
>
> For now I have one JMX file for each request and one threadgroup for the
> different steps of users (5 thread groups). Where each threadgroup have the
> exact same result collectors.
>
> I have experimentet a bit with User Defined Variables (UDV). It seems I
> need some way to let one variable reference a set/list of values.
>
> The setup now is too hard to maintain due to duplicated configuration.
>
>
>
> I am familiar with Maven and the maven-jmeter-plugin. I can handle ONE of
> these dimensions using different executions, but I cannot handle two and
> this is not a very elegant solution.
>
> The resources I have looked at are listed at
>
> http://wiki.community.objectware.no/display/smidigtonull/JMeter+configuration
>
>
> Thanks in advance.
>
> --
> Best regards
> Erik Drolshammer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to