jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: __CSVRead behaviour with sample failures
Date Thu, 25 Nov 2004 16:39:56 GMT
You need to ensure that you call CSVRead once with the "next"
parameter at the end of each set of data you want to use. Otherwise
the wrong data is likely to be returned.

It's best to do all the extraction of parameters in a User Parameters

as that loads all of the values at once, and it loads them in order of
the fields on the screen.

Then refer to the variables as needed in the samplers.

On Thu, 25 Nov 2004 16:17:41 -0000, Ashley Hayes
<> wrote:
> Hi,
> I seem to be experiencing the follow behaviour of the CSVRead function. If a
> Http  sampler error occurs and the ThreadGroup is configured to "Action to
> be taken after a Sampler error" as  "continue" , then the "current row" of
> the CSV file is not updated correctly, e.g. the values in the row that
> caused the error are used again.
> If I choose to "Stop Thread"  ( for "Action to be taken after a Sampler
> error") then the values of that row seem to be skipped.
> My understanding is that, each iteration of each thread will get a different
> (possibly unique) row, e.g.
>          Thread group of 20, Test Plan of 5 iterations and 100 rows in CSV,
> therefore each iteration will read a unique row from the CSV file. Is my
> understanding correct? If so I presume this behaviour should hold even if a
> sampler error occurs?
>         I'm using Jmeter 2.0.1. My test plan defines some "User Parameters"
> that get their values from a CSV file,  ${__CSVRead(myusers.csv,0)}, its
> checked to "update Once per iteration".
> Thanks for your time,
> Ashley
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message