Author: sebb
Date: Sat Oct 11 08:36:36 2008
New Revision: 703676

URL: http://svn.apache.org/viewvc?rev=703676&view=rev
Log:
How to use CSV Data files per thread

Modified:
    jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml

Modified: jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml
URL: 
http://svn.apache.org/viewvc/jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml?rev=703676&r1=703675&r2=703676&view=diff
==============================================================================
--- jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml (original)
+++ jakarta/jmeter/trunk/xdocs/usermanual/component_reference.xml Sat Oct 11 
08:36:36 2008
@@ -2336,10 +2336,17 @@
        </p>
        <p>
        By default, the file is only opened once, and each thread will use a 
different line from the file.
-       See the description of the Share mode below for additional options 
(JMeter 2.3.2+).
+       However the order in which lines are passed to threads depends on the 
order in which they execute,
+       which may vary between iterations.
        Lines are read at the start of each test iteration.
     The file name and mode are resolved in the first iteration.
        </p>
+       <p>
+       See the description of the Share mode below for additional options 
(JMeter 2.3.2+).
+       If you want each thread to have its own set of values, then you will 
need to create a set of files,
+       one for each thread. For example test1.csv, test2.csv,... testn.csv. 
Use the filename 
+       <code>test${__threadNum}.csv</code> and set the "Sharing mode" to 
"Current thread".
+       </p>
        <note>CSV Dataset variables are defined at the start of each test 
iteration.
        As this is after configuration processing is completed,
        they cannot be used for some configuration items - such as JDBC Config 
- 



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to