Newman: Folder parameter behavior change in 3.9.0

Created on 6 Dec 2017  路  4Comments  路  Source: postmanlabs/newman

Did the behavior of --folder parameter change on minor version release?

Version and environment information:

  1. Newman Version: 3.8.3 - 3.9.0
  2. OS details: windows 7 x64
  3. CLI
  4. Did you encounter this recently, or has this bug always been there: recently
  5. Expected behaviour: folder parameter runs the specified folder, not returning 0 tests run
  6. Command / script used to run Newman: newman run col.postman_collection.json --folder direct_read_only
  7. Sample collection, and auxilliary files: col.postman_collection.json.txt
  8. Screenshots: none

Steps to reproduce the problem:

  1. npm install -g [email protected]
  2. newman run col.postman_collection.json --folder direct_read_only
  3. 1 execution
  4. npm install -g [email protected]
  5. newman run col.postman_collection.json --folder direct_read_only
  6. no executions

Most helpful comment

Hey @al-tr, we are working on fixing this issue, you can track progress in #1326.
Thanks for your patience.

All 4 comments

Hey @al-tr, thanks for reporting this. I was able to reproduce this issue locally where even if the supplied folder name exists, newman just gracefully exits without executing the requests in that item group. Will keep you updated on it.

Hey @al-tr, we are working on fixing this issue, you can track progress in #1326.
Thanks for your patience.

Hey @al-tr, this has been fixed and released in 3.9.1. Go ahead and try it and feel free to reach out in case you have any other queries. :smile:

@deepakpathania works weel, thanks, all builds are using the latest vesion again :hammer_and_wrench:

Was this page helpful?
0 / 5 - 0 ratings

Related issues

genxlogics picture genxlogics  路  4Comments

gaieges picture gaieges  路  4Comments

DotNetRockStar picture DotNetRockStar  路  5Comments

Schveitzer picture Schveitzer  路  4Comments

brimchan picture brimchan  路  3Comments