You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a meta jmx file that uses the Include Controller that includes all scripts for individual projects. This a useful layout for when you have many projects going through a single gateway. I use the individual jmx files for testing individual APIs, then include them in the meta jmx file for the biblical, full load tests.
jmeter-ec2 doesn't recognize the Include Controller for things like thread management/etc, and thats probably ok as it may add a lot of complexity. Also since it copies the jmx file from the $project/jmx/meta.jmx to /tmp/execute.jmx on the remote host, the include controller gets confused as the layout locally is different than the layout remotely. (../data/ vs data/)
Work around is to copy the included jmx files into the data/ dir and as that layout matches the layout on the remote server. I have a simple bash script to copy the jmx files and the csv files into the data dir.
Eg:
project/
- meta.jmx
data/
- foo.jmx
- bar.jmx
- foo.csv
- bar.csv
results/
jmx/
- meta.jmx # Same as above
Not really a feature request but more a work around if anyone has the same issue and to show how i worked around the issue.
The text was updated successfully, but these errors were encountered:
Thanks Eric, this is helpful. I'm just starting to look at modifying this script for my current project and this was one of the first questions which came to mind.
I have a
meta
jmx file that uses theInclude Controller
that includes all scripts for individual projects. This a useful layout for when you have many projects going through a single gateway. I use the individual jmx files for testing individual APIs, then include them in themeta
jmx file for the biblical, full load tests.jmeter-ec2 doesn't recognize the
Include Controller
for things like thread management/etc, and thats probably ok as it may add a lot of complexity. Also since it copies the jmx file from the$project/jmx/meta.jmx
to/tmp/execute.jmx
on the remote host, the include controller gets confused as the layout locally is different than the layout remotely. (../data/
vsdata/
)Work around is to copy the included jmx files into the data/ dir and as that layout matches the layout on the remote server. I have a simple bash script to copy the jmx files and the csv files into the data dir.
Eg:
Not really a feature request but more a work around if anyone has the same issue and to show how i worked around the issue.
The text was updated successfully, but these errors were encountered: