-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Running collection with packages results in pm.require
is not a function
#3229
Comments
I'm having the same issue with the following info; Newman Version (can be found via newman -v): 6.1.2 |
When is the package management feature in postman going to be supported in newman? |
The Library feature is almost useless for us currently, because we develop in postman and run in newman. |
I would also like to use this with newman since we use newman. |
Same for me. Thanks. |
+1 |
We implemented this using UI with Postman and it's a great feature to have a better maintainbility of the code. Having it in newman would be a great pro. |
It's a good feature, very helpful for improving the maintenance of the API tests but... on the automated side, using newman is mandatory to have this feature. I hope it will be available with newman usage also |
It didn't even cross my mind that newman wouldn't support this! Any timeframe for this to be implemented? |
I mean, if you can't use it using |
Some problem here. Upvoted! |
Some problem, please implement in newman or postman-cli |
Same here, would be nice to have it in newman, too |
Hi, could you prioritise it a little higher? please ;-) |
Hello, thank you for your excellent work, and I agree, it would be really nice to have this feature, for better maintainability. Upvoted |
Would like this feature very much. Was surprised when I found out it wasn't supported. |
Any updates on this? |
newman -v
): 6.1.2newman run clients-api-collection.json -e cloud-dev-environment.json
01. TypeError pm.require is not a function at test-script inside "[Test Setup] / CreateNewClient"
The text was updated successfully, but these errors were encountered: