I made this way: declared a test plan variable that retrieved a parameter
value with the folder containing data files.
At distributed testing, pass that parameter using -G directive and it's
done.
Test Plan Variables
csv.path | ${__P(csv.path,
/default/path/to/folder/including/trailling/path/separator/)}
CSV Data Config
filename = ${csv.path}filename.csv
jmeter.sh
-Jcsv.path=/my/local/folder/
or
-Jcsv.path=C:\my\local\folder\
Distributed test
-Gcsv.path=/root/csvs/
or
-Gcsv.path=D:\jmeter\csvs\
or
define the distributed test folder as default value in ${__P()} expression
and no need to use -G directive
Regards.
Flavio Cysne
2012/2/2 sergio <[email protected]>
> Il 02/02/2012 06:10, Deepak Shetty ha scritto:
>
> I believe relative paths are relative to the script location
>>
> No.
> In my experience, the path is relative to the directory from where you
> launch Jmeter.
>
> I usually keep all project data (.kmx, .csv and so on) in a single
> directory. I go there and I launch with a command like:
> c:\Program_files\jakarta-**jmeter-2.5\bin\jmeter.bat
>
> This can be useful if you need to launch more than one instance on a
> single machine...
>
> regards
> Sergio
>
>
>
>
> regards
>> deepak
>>
>> On Wed, Feb 1, 2012 at 9:05 PM, rajan gupta<[email protected]>
>> wrote:
>>
>> Hi
>>>
>>> This is just for any googler facing issue with CSV Data Set element.
>>> Per documentation it says if csv file is in bin folder it is enough to
>>> give
>>> filename. It did not work for me, even if it is jmeter bin directory I
>>> had
>>> to give full path to the csv file.
>>>
>>> Not sure if this is a known issue or just happened to me.
>>>
>>> Thanks
>>> Rajan
>>>
>>>
>
> --
>
> Ing. Sergio Boso
>
> Mail:
> Web:
> PEC:
> Cell:
> Linkedin:
> Skype:
>
>
>
> [email protected] <mailto:[email protected]>
> www.bosoconsulting.it
> [email protected] <mailto:[email protected]>
> +39 335 7243 445
> http://it.linkedin.com/in/**sergioboso<http://it.linkedin.com/in/sergioboso><
> http://www.linkedin.com/pub/**sergio-boso/1/29b/255<http://www.linkedin.com/pub/sergio-boso/1/29b/255>
> >
> sbos61
>
> In caso di erronea ricezione da parte di persona diversa, siete pregati di
> eliminare il messaggio e i suoi allegati in modo definitivo dai vostri
> archivi e di volercelo comunicare immediatamente restituendoci il messaggio
> via e-mail al seguente
> indirizzosergio@**bosoconsulting.it<[email protected]><mailto:
> [email protected]>
> L’interessato può, inoltre, esercitare tutti i diritti di accesso sui
> propri dati previsti dal decreto 196/2003, tra i quali i diritti di
> rettifica, aggiornamento e cancellazione, inviando un messaggio all’
> indirizzo:sergio@**bosoconsulting.it<indirizzo%[email protected]><mailto:
> [email protected]>
>
>
>
>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> user-unsubscribe@jmeter.**apache.org<[email protected]>
> For additional commands, e-mail: [email protected]
>
>
