Newman: Add support to run newman from yaml files

Created on 28 Oct 2017  路  4Comments  路  Source: postmanlabs/newman

This is simply a feature request to support the ability to run yaml files (both collections and environments) via newman in the same way that json is run.

The benefit that this would provide is to allow for easier access to modify and write postman files by hand instead of having to manage the json syntax, which could then be used to convert on the fly and upload to postman api

@macejiko

feature request

Most helpful comment

@benhowes - thanks for sharing that .. looks pretty great and addresses some of the issues that we've had with the json aspect of newman/postman.

Just for some additional color here, we're having a tricky time getting developers to engage in using postman even after building some framework'ing that integrates it into our CI. My assumption is that since it's not native to a text editor (especially coming in as a non-postman user), and easily understood by reading the collection files, that barrier to entry is high and not worth the ramp up, which leads to only a few people managing tests which is recipe for trouble.

This ticket was intended to help ease that, and Tavern looks like it may too.

All 4 comments

Could you provide more context on how this is useful? You can use the Postman app to interact with collections in a streamlined manner.

Readability of the files (ie if i dont want to use the app).

As an example we use postman collections to perform monitoring and testing of our apps, and changing a test or making an additional request is a lot harder via json than it is with yaml.

@gaieges we built tavern for exactly this reason (plus a few others). https://taverntesting.github.io/

@benhowes - thanks for sharing that .. looks pretty great and addresses some of the issues that we've had with the json aspect of newman/postman.

Just for some additional color here, we're having a tricky time getting developers to engage in using postman even after building some framework'ing that integrates it into our CI. My assumption is that since it's not native to a text editor (especially coming in as a non-postman user), and easily understood by reading the collection files, that barrier to entry is high and not worth the ramp up, which leads to only a few people managing tests which is recipe for trouble.

This ticket was intended to help ease that, and Tavern looks like it may too.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

estebancoria picture estebancoria  路  4Comments

vbtelus picture vbtelus  路  3Comments

AlphaWong picture AlphaWong  路  3Comments

Pixcell picture Pixcell  路  3Comments

hvitis picture hvitis  路  5Comments