postmanlabs
Newman updates
Hi, I opened a support request to Postman to find out if this repository is maintained at all. They said yes and to be able to track the new changes, I should open an issue here. So here it is.
My original support request (#235539):
Hello,
We are using newman in our CI to run our Postman collection. I noticed a long time ago, that when I use newman, a deprecation warning was coming:
(node:11184) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
It try to keep all my packages up-to-date, but it seems that this warning is coming from postman packages:
└─┬ [email protected] ├─┬ @postman/[email protected] │ ├─┬ [email protected] │ │ └── [email protected] deduped │ └── [email protected] ├─┬ [email protected] │ └─┬ [email protected] │ └── [email protected] deduped └─┬ [email protected] └─┬ [email protected] └─┬ [email protected] └─┬ [email protected] └── [email protected] deduped
I checked the newman repository (https://github.com/postmanlabs/newman) and the last update was 7 months ago there. There's a lot of issues and PRs open. Is this repository maintained at all? If not newman, what else can be used in CI to run the collections, which can run them locally (not using cloud)?
Linking another issue with other deprecation warnings: https://github.com/postmanlabs/newman/issues/3289
Have you tried using Postman CLI?
https://blog.postman.com/postman-cli-vs-newman/
https://learning.postman.com/docs/postman-cli/postman-cli-overview/
Postman CLI is not good enough for our need. In the support ticket I explained why, but I paste it here as well:
Our collections and environment variables are saved in our repository, next to the code, so it is under version control and no need to maintain the tests in a separate place. It's strait forward and a big help to the developers who can run all tests with one command and no need to switch tools. I was happy with newman, because it's fast and it has an html reporting, the package is small enough and doesn't require resources. Also, it is very useful if a developer can run the test without internet (on an airplane or if they don't have access to internet). Our platform can be setup locally (no internet required) and I prefer if all the tests can be run offline as well. Internet must not be a bottleneck for testing. As the company's QA I try to make all tests available and accessible on all environments, otherwise I can't expect from the devs to run the tests.