JMX file upload issue when using the scenario ID as JMX filename

[sureshsuru]

This is specific to JMeter and haven't tested with other tools. When a scenario is created on DLT and JMeter script (JMX file) is uploaded and a first test is run, the JMX file gets a name (irrespective of whatever the name was during upload). If the script is downloaded from this scenario and changes are made to the downloaded script and we try to do another run, by clicking on "Edit Scenario" and try to upload the updated script, the updated script does not get uploaded (which is not visible in the UI, but visible based on the test results) and the scenario runs a previous version of the script.

**

1. Create a JMeter script (say Test.jmx) with a 'Thread Group' and a 'jp@gc - Dummy Sampler' on the local computer.
2. Rename the sampler label as 'jp@gc - Dummy Sampler - 1'.
3. Save the script and upload it to DLT to do your first run.
4. On DLT, the script gets the name of the scenario ID of the scenario to which the script gets uploaded. For example, if the scenario ID is rndpqkYR7L, then the script name would be rndpqkYR7L.jmx. Note this as version 1 of the script.
5. For the next run, instead of making updates to Test.jmx on the local computer, download a copy of the script from DLT from the scenario (rndpqkYR7L.jmx).
6. Make a change to the downloaded script (rndpqkYR7L.jmx) by renaming 'jp@gc - Dummy Sampler - 1' as 'jp@gc - Dummy Sampler - 2'. Note this as version 2 of the script
7. Upload it to the same scenario on DLT (with the same name rndpqkYR7L.jmx) and do a second test run.
8. Compare the results of both the test runs, the test results will only show 'jp@gc - Dummy Sampler - 1' but not 'jp@gc - Dummy Sampler - 2'.
   **

Expected behavior: On 'Step 7', version 2 of the script must get uploaded.

Please complete the following information about the solution:

• Version: v4.0.13
• Region: ca-central-1
• Was the solution modified from the version published on this repository? No
• If the answer to the previous question was yes, are the changes available on GitHub? NA
• Have you checked your [service quotas] (https://docs.aws.amazon.com/general/latest/gr/aws_service_limits.html) for the services this solution uses? Yes
• Were there any errors in the CloudWatch Logs? Unsure

Screenshots

Additional context

[daznian]

Thanks for reporting the bug. We are looking into this issue.
In the meantime, the following work-around should work:
When re-uploading the test file for a new test run, do not use the same name as the already uploaded test, but update to a new name. That should ensure the test script is updated properly.