Where on a remote workstation should I put the CSV configuration file for JMeter distributed testing?

Question

I want JMeter to distribute testing. The manual said that first I have to start jmeter-server on the remote nodes, and then I have to update jmeter.config and run jmeter on the main node.

I have done all these steps. My test plan includes working with CSV configuration files. If I test only 1 (master) node - then everything works like a charm. But when I try to distribute testing, all tests fail. Some research has shown that remote hosts send requests without substituting ${..} -like parameters. Requests look like

POST data: 5 | 0 | 6 | Http: //host.com/portal/ | 67D1C612DCF291DCD0F71AD15E404F37 | host.ui.client.services.LoginService | Login | java.lang.String / 2004016611 | $ {admin_login} | 1 | 2 | 3 | 4 | 3 | 5 | 5 | 5 | 6 | 6 | 1 |

Obviously, the remote jmeter-server cannot find the CSV file. Where should I put this?

PS: I have machines with different OS (Windows 7 and Ubuntu 10.04).

Answer 1

The easiest way to solve the problem with multiple operating systems is to put the CSV file in the Jmeter BIN directory on all test machines and not refer to the path in the Config component for the CSV dataset.

Answer 2

Place the full path and file name in the CSV Dataset Configuration component, for example. c:\loadtest\config.csv and make sure you put the CSV file in the specified location.

---

The manual components also indicate the following:

Relative file names are resolved relative to the path of the active test plan.

Therefore, it should be possible to place the file in the same directory as the test plan file. This should work on both Linux and Windows.

Answer 3

Any link to a data file assumes that such a file exists in the corresponding nodes on the specified path. For example, if you have CSV files in C: \ data, then when executing the test plan in a distributed way, the test plan will look for the data file in C: \ data node (slave).

In fact, if you use 10 slave machines, you need to have the c: \ data folder on all of these 10 machines.

No need to copy a test plan.

Answer 4

EDITED , because the link to the documents was wrong - I was burnt by my own answer :)

Old question, but I just ran into this problem, and the answers here are contradictory.

Is the relative path permitted for the bin / directory or the directory of the current .jmx script?

Answer: this is only a script test directory. From the docs:

Relative file names are resolved with respect to the path of the active test plan. Absolute file names are also supported, but note that they are unlikely to work in remote unless the remote server has the same directory structure. If the same physical file is referenced in two different ways - for example, csvdata.txt and. /csvdata.txt - then they are treated as different files. If the OS does not distinguish between upper and lower case, csvData.TXT will also open separately.