quote author="sebb-2-2"> ... > 2) How can I set up input numbered variables that the For Each controller > needs to use. I know all the values I want to use inadvance. Is it as > simple > as setting them up as UDVs on the Test Plan itself and avoid the CSV all > together?! Just thought of doing that and will try it in the morning!!
Yes, that would be simpler. Sebb, following on from the comment above I've set up the ForEach Controller and variables as shown and it works a treat folderpathseta.properties file: folder1=/Temp/Folder1 folder2=/Temp/Folder2 TP (UDV: NAME:folder_1 VALUE:${__property(folder1)} NAME:folder_2 VALUE:${__property(folder2)} --TG (2 thread, 2 RU, 2 Loop) --ForEachController (INPUT:folder OUPUT:browsePath) ----Java Sampler ${browsePath} Using individual properties file e.g. folderpathseta.properties (loaded with the -q command line option) allows me to change the actual folder paths used by any test...easier than having to update the UDV GUI. Thanks for the help guys. -- View this message in context: http://www.nabble.com/Simple-csv-input-data-iteration---all-threads-using-same-value-tp17101828p17127303.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]