-
Notifications
You must be signed in to change notification settings - Fork 51
Dynamic Variables #90
Comments
Hi @dbacelar4i I have created a PR to provide full support of all Postman dynamic variables. So keep an eye out of the progress of the PR. |
For those experiencing the same issue, I have provided a forked NPM package version that contains this fix: Replace in your packages.json:
to
This is a forked NPM package, to provide this new feature. The current maintainers are quite overloaded by the acquisition of K6 by Grafana. By forking the repo & package, users can keep using new PR's & (security) fixes. At a later stage the changes can potentially be merged back in the original postman-to-k6 repo. The changelog contains the differences between the original package & the forked version. |
Apologies for the inactivity on this project. Due to the inability to properly support this project, the k6 team has decided not to continue its development. The primary reason is that k6 scope has grown significantly with the launch of k6 extensions. The team is prioritizing extending k6 capabilities over the converters. We suggest you post your issue at api-deck/postman-to-k6. The project is active and maintained on this fork. |
Hi,
I have a problem with dynamic variables like:
{{$randomFirtsName}}, {{$randomLatitude}}, {{$randomLongitude}}, {{$randomColor}}, {{$randomCity}}, {{$randomCountry}}, {{$randomAdjective}}, {{$randomFileName}}
After conversion, they are not recognized and cause an error when performing the load test.
The text was updated successfully, but these errors were encountered: