Postman CLI generates a junit file report

[diegofernandon]

Is there an existing request for this feature?

• [X] I have searched the existing issues for this feature request and I know that duplicates will be closed

Is your feature request related to a problem?

NA

Describe the solution you'd like

As newman does, it would be useful having the possibility to generate a junit file report from Postman CLI. It is amazing the integration with Azure DevOps pipeline releases but sometimes we have stakeholders not added to the postman team who want to see the test results directly in Azure DevOps.

Describe alternatives you've considered

Generates a junit file or a json file with the test results as an additional parameter in the command line execution

Additional context

No response

[malvikach]

@diegofernandon thanks for sharing the feedback. We have taken note of this feature request. We will share updates on this when we pick this up in our roadmap.

[diegofernandon]

Sounds great, thank you!

[julian-alarcon]

A suggestion added to output formats would be to generate a JSON output file with output of postman api lint commands instead of a table.

[GrayedFox]

Not being able to generate any sort of report (JSON, jMeter, or otherwise) when using postman-cli instead of newmann is a big pain point for us.

We want to use the Postman app (GUI app) to manage our collections and write and edit tests - a little bit like treating the Postman app as a dedicated IDE for writing some kinds of tests for our API (usually smoke and contract tests). It's also useful for me as a teaching aide - I'm responsible for up-skilling and mentoring a team of QEs as the QE Engineering Lead - and being able to also document and describe collections using markdown is another good win here.

But the big missing piece is the ability to generate meaningful automation/collection reports.

If using postman-cli to run the tests our development feedback loop is this:

• update requests/collection/tests
• run collection using postman-cli
• monitor results in terminal

If using newmann our development feedback loop is this:

• update requests/collection/tests
• export collection
• export environment (if needed)
• run collection using newmann
• monitor results in terminal
• generate a report (if needed)

It is often the case that we want to share results locally. Sometimes it's just so I can read through the raw data myself, but we might also want to plug that data into a dedicated monitoring or logging platform at some point like NewRelic, Kibana, or something else entirely.

The point is - postman-cli locks us into using Postman Cloud and that's a big problem.

Newmann does not, but the developer experience is worse: these few extra steps makes using Postman as the gatekeeper for certain kinds of automation much less attractive for our team.

Postman is still a good testing tool, but if I need to set up a dedicated repository or testing project for these types of tests to be run in the cloud then I'll just end up going all in, in which case it makes more sense for us to just write all of our API tests using jest/Pact/pick-a-framework - since the whole point of using postman and postman-cli together is so that our API testing tool supersedes the need for separate processes for documenting and automating our API, wherever and whenever possible.

If we need to use a different CLI tool locally for debugging than the one used in our CI/CD pipelines, that's more overhead and maintenance, and Postman lands squarely back in the realm of "good for manual testing/API development" only, as opposed to something that props up our automation efforts.