newman: Requests made by Newman are erroring (Latest version 6.2.0)

  1. Newman Version (can be found via newman -v): 6.2.0
  2. OS details (type, version, and architecture): Edition Windows 10 Business Version 22H2 OS build 19045.4651 Experience Windows Feature Experience Pack 1000.19060.1000.0 Processor 11th Gen Intel® Core™ i7-1185G7 @ 3.00GHz 1.80 GHz Installed RAM 16.0 GB (15.7 GB usable) System type 64-bit operating system, x64-based processor
  3. Are you using Newman as a library, or via the CLI? CLI
  4. Did you encounter this recently, or has this bug always been there: since v6.2.0
  5. Expected behaviour: get a 200 response
  6. Command / script used to run Newman: from batch file
 @echo off
set postmanPath=C:\somedir
set "postmanCollection="%postmanPath%\_test.postman_collection.json""
call newman run %postmanCollection% ^
--insecure
pause
  1. Sample collection, and auxiliary files (minus the sensitive details): _test.postman_collection.json
  2. Screenshots (if applicable): image

Steps to reproduce the problem:

  1. Save the code above to a batch file
  2. run the batch file

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 19 (6 by maintainers)

Commits related to this issue

Most upvoted comments

Might be a similar issue, newman 6.2.0 now is hanging with this output until force quit:

error: Cannot read properties of undefined (reading 'exec')

Downgrading to 6.1.3 and all works fine.

newman-error

I have a similar issue with 6.2.0 that only concerns https requests towards a public server (not on localhost) with a DigiCert wildcard SSL certificate. Specifying -k or --insecure did not fix the issue. It hangs at the first POST https request it does and I have to force quit it.

Changing the environment file such that the base url is http instead of https makes it work fine.

Downgrading to 6.1.3 also fixes the issue with https. That is my current workaround.

PS: Using curl https://xxx.xxxxxxxxxxxxxxx.xx/api/company.json works fine.

root@37eb535dc670:/home/node# newman run ext.json -e env.json -r cli,junit -k
newman

testSuiteExtensive

❏ Setup users
↳ check that a company can be added
  POST https://xxx.xxxxxxxxxxxxxxx.xx/api/company.json ⠋^C

Spent half a day troubleshooting this issue. Please note that we get the same issue and it is a collection that used to work. Just changed the version from 6.2.0 to 6.1.3 and it is back to working now.