The user-provided path does not exist.
chir050 opened this issue · 9 comments
Describe the bug
Random CSV Data Set Plugin seems to be not working with new version v3.2.4.
The test are failed with message The user-provided path file.csv does not exist.
To Reproduce
- use jmeter with Random CSV Data Set Plugin
- create file.csv and jmeter.jmx in the same folder.
- in jmeter set relative path to file.csv
- zip entire folder
- upload zip and run dlt test.
Expected behavior
The file.csv should be found.
Please complete the following information about the solution:
- Version: v3.2.4
- Region: eu-central-1
- Was the solution modified from the version published on this repository?
- If the answer to the previous question was yes, are the changes available on GitHub?
- Have you checked your service quotas for the services this solution uses?
- Were there any errors in the CloudWatch Logs? The user-provided path file.csv does not exist.
Screenshots
Hi,
I cannot create this issue in my end. I need more info on what the jmx content is, cause this has been particularly tested and it is working.
Also make sure that in your jmx script create the csv filename is ./file.csv and not file.csv This could also fix the issue.
@kamyarz-aws Thanks for the suggestion, i'll give a try.
here is my test scenario, the endpoints have been changed but I don't think that should be a problem.
I noticed there are plugins that needs to be installed.
These are the plugins if I am not wrong:
jmeter-parallel-0.11.jar
jmeter-plugins-random-csv-data-set-0.8.jar
jmeter-plugins-tst-2.6.jar
these will install Install plugin:
bzm-random-csv 0.8
Install plugin: jpgc-tst 2.6
Install plugin: bzm-parallel 0.11
Now when you run in Jmeter it does the automatic installation for you but for our tool, you need to provide the Jar file as part of the zip file. To do so, locate the jar files or download them. Create a plugins folder in your test folder. Add the jar files to that folder. Zip your folder alongside your testplan and inputs and this should work.
As far as it is known to me Taurus of AWS DLT installs most plugins automatically without manual need. I have no problem using AWS DLT version 3.2.2 to run the same test scenario. The bug only applies to the latest version, which is 3.2.4 (not tested 3.2.3).
The plugins are loaded normally, otherwise you get other error messages. Does this mean now that the plugins loaded from Taurus have a different location compared to the plugin folder?
If this has changed in the latest version then I would try to use plugin folder.
For now use the plugins folder- we will investigate this.
@ chir050 The release is out. Please check if your issue is resolved. I particularly ran your script for this and seemed to be okay
@kamyarz-aws Thank you, it worked perfectly. Have a nice day!