search

aws-solutions / distributed-load-testing-on-aws

Distributed Load Testing on AWS
https://aws.amazon.com/solutions/implementations/distributed-load-testing-on-aws/
Other
324 stars 118 forks source link

Add sequential number as JMeter property to the execution engines for the identification of engine from the JMeter script. #101

Open tpark-itops opened 1 year ago

tpark-itops commented 1 year ago

Is your feature request related to a problem? Please describe. We have requirement to use unique users to complete the execution of the test. The user should not be used concurrently amongst execution engines (containers). Apparently, currently version of DLT support neither splitting up users from a single input file (CSV file) nor uploading separate input file for each execution engines to consume.

Describe the feature you'd like Add sequential number as JMeter property in each of the execution engine/containers, so that the number could be used in JMeter function for reading the input file designated for the engine. For example, in case of two engines (containers), we can upload files named file1.csv and file2.csv. In the CSV Filename field you should specify: file${__P(TAURUS_SESSIONS_INDEX)}.csv.

Additional context Reference https://guide.blazemeter.com/hc/en-us/articles/206733699-How-to-setup-a-different-CSV-file-for-each-JMeter-engine-

G-Lenz commented 1 year ago

Thank you for the request, we will add this to our backlog so that we may plan on researching this feature in the future.

tpark-itops commented 1 year ago

Thanks for your response. FYI, I was able to retrieve all parameters passed to the task/containers from TaskRunner lambda function via using __env function in a JMeter script. Those parameters include S3_BUCKET, TEST_ID, TEST_TYPE, FILE_TYPE, PREFIX, and SCRIPT.

serdarbuyuran commented 1 year ago

I'm waiting for this feature to come. Thanks for your support.