Thim

@yjose I think that everything is ready. I cant see the change request that was asked, which seems more a Github issue on my end. I'm using this PR since...

@KensingtonTech This how my servers object looks like: ``` "servers": [ { "url": "{baseUrl}", "variables": { "baseUrl": { "default": "https://acme.com", "description": "Base URL domain" } } } ], ``` There...

Hi @jekakos Postman excludes "default" headers from the export, which results in missing headers when making the requests. Have a look at: https://github.com/apideck-libraries/postman-to-k6/discussions/42#discussioncomment-2271512 >> Missing headers. The item also mentions...

If the work-a-round helped, feel free to close the issue.

@svmundada The documented "unsupported" features were taken over from the original repo. I'll review the list of features, since `pm.response.to.have.status` is working. With regards to brining support for these features,...

@Kpizzle The pre-request scripts are supported, but the "pm.sendRequest" would be more difficult, since this concept does not really exist in the K6 concepts. As a work-around I do it...

FYI: I have collected your question in the "[discussions](https://github.com/apideck-libraries/postman-to-k6/discussions/54)" section for future reference.

hi @kgrozdanovski I can investigate to see what is needed to bring the support. Could you share an example of what you would do with the pm.response.headers.*?

Correct, currently the postman-to-k6 library is not fully capable of handling "files". I still have to investigate if this is a bug or feature. If anybody has a solution, feel...

hi @reinaldorossetti Could you share your Postman collection and postman-to-k6 configuration? That way we can use it to reproduce the faulty behaviour, which will allow us to debug & potentially...