It's certainly possible to use a property to specify the number of threads.
So functions work, i.e. CSVRead will work.
The count should be placed in the first row of the CSV file.
Try the following (tested):
${__CSVRead(test.txt,0)}${__CSVRead(test.txt,next)}
Should also work for the ramp-up loop count if needed (not tested).
There is no guarantee that fields will be read in the same order in
each release, so all the values must be columns in the first row.
And you will either need to experiment to find which field should have
the "next" in it, or put it as the first entry in the UP
Pre-Processor.
The rest of the file can then be read in a User Parameters (UP)
Pre-processor or in samplers etc.
But it may be simpler to pass in the thread group settings as
properties, so you can use the same test file for different
variations, e.g.
1 thread, 10 loops
2 threads 5 loops
etc
S.
On 6/1/05, Sander Stevens <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Maybe a nice idea (because I think it is not possible yet):
>
> I am using JMeter as a functional test tool with Excel (csv) as input for my
> test cases. In this way I have to set the number of threads to the number of
> rows in my excel sheet. No problem, but it would be nice if this is filled
> automatically. Just to follow the excel sheet, even if there are test cases
> (rows) added or deleted. The way I am thinking is the following: I count the
> rows in the excel sheet (excel function COUNT). Place the number of rows
> somewhere in the sheet, read this value with function __CSVRead (e.g. rows)
> and use this value to notify the number of threads (${rows}).
>
> Would that be a nice feature?
>
>
>
> Met Vriendelijke Groet,
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
