The iterative mode of the value
CSV data set config For data iteration, the official website is explained as follows:
By default, the file is only opened once, and each thread will use a different line from the file. 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.
In other words, the CSV file is opened only once during the entire script run, and the values of each thread start from the beginning of the file. The order of data iteration between threads does not affect each other.
Multiple threads are using different data
If there is such A test scenario, change the state of an A record, but cannot amend the state to the current state, this time, you can change the state to state. A, B then change state to state, and in this way, it can’t happen different threads to get the same value, for different thread configuration data of different iterations.
The official website provides a way to configure different CSV files for different threads:
See the description of the Share mode below for additional options. 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 test${__threadNum}.csv and set the “Sharing mode” to “Current thread”.
Name the file test1.csv, test2.csv
CSV data set config, filename is set to test${__threadNum}.csv,
How do I configure CSV files for distributed tests
Set filename to the absolute path, and then place the CSV files under the same file on each loader.