Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
tpark-itops opened this issue Aug 31, 2022 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@tpark-itops
Copy link

tpark-itops commented Aug 31, 2022

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-

@tpark-itops tpark-itops added the enhancement New feature or request label Aug 31, 2022
@G-Lenz
Copy link
Contributor

G-Lenz commented Sep 1, 2022

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
Copy link
Author

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants