authorjapps / authorjapps/zerocode-hello-world
Unable to parameterized filename - Performance Testing
- Dominant language
- Java
- Stars
- 18
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
**Description** :
In order to execute performance tests, json has to be sent in the body request.
There are more than 1000 json files that has to be used in the performance testing.
Each file contains different data. File name consists of <> format
We created custom java function that will scan the directory for list of files and parse the uuid so that it can be used in the testing scenario
**Challenge**:
Zerocode step does not allow parameterization of file names
For example, in below request, 40000000000000000123456789ABCDEF cannot be parameterize
**Benefits**:
Adding this feature will allow execution of performance test using zerocode framework for the given scenario
**Sample Steps:**
- name: get_geid
url: ListFilesExecutor
operation: getListOfGeid
assertions:
geid: $IS.NOTNULL
body: $IS.NOTNULL
- name: post_endpoint
url: /client
method: POST
request:
headers:
uuid: ${$.get_geid.response.geid}
body: ${JSON.FILE:reusableContent/request/**40000000000000000123456789ABCDEF**-client.json} //Unable to parameterize this step
verify:
status: 200
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing how the JSON.FILE path is resolved in the sample post_endpoint step and how values from get_geid are substituted. Define the supported filename parameter syntax, then verify that the UUID-based path resolves to the intended request file and remains usable in the performance-testing scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100