Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Newman could not find "cli junit" reporter #2205

Closed
DaveMacNeil opened this issue Jan 7, 2020 · 3 comments · May be fixed by #2937
Closed

Newman could not find "cli junit" reporter #2205

DaveMacNeil opened this issue Jan 7, 2020 · 3 comments · May be fixed by #2937

Comments

@DaveMacNeil
Copy link

  1. Newman Version (can be found via newman -v): 4.5.7 & 4.5.6 (failing on both)
  2. OS details (type, version, and architecture): Windows 10 Pro v.1803 OS Build 17134.765
  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: Recently (Started in builds Dec 30th.)
  5. Expected behaviour: Newman to run and publish results via Junit
  6. Command / script used to run Newman: Running through Azure Devops on local machine
    Step Install newman
    npm install -g newman
    Step Run newman
    newman run '$(Build.SourcesDirectory)/PostmanTests/Collections/API Integration Tests.postman_collection.json' -e '$(Build.SourcesDirectory)/PostmanTests/Environments/Development.postman_environment.json' --insecure -r cli,junit
  7. Sample collection, and auxiliary files (minus the sensitive details):
  8. Screenshots (if applicable):

  • The pipeline
    2020-01-07 10_24_09-2020-01-07 10_14_34-Window

  • Newman installed on the machine
    2020-01-07 10_15_45-Window

  • The reporter
    2020-01-07 10_16_39-Window

Steps to reproduce the problem:

  1. Install newman globally
  2. Run newman against a collection with -r cli,junit

I have searched through open and closed issues, but only found #1969 which refers to an external reporter.

This build pipeline has been working for over a year, until it started failing on Dec. 30th, 2019.
@palprabhat
Copy link

I was having the same issue earlier while trying to use cli,json, fixed it by using quotes around it.
newman run $runnerFileFullName -e $environmentFileFullName --disable-unicode --color off --reporters 'cli,json' --reporter-json-export $reportFile

@DaveMacNeil
Copy link
Author

@palprabhat Huh, yea that did it for me too. Newman needs updated documentation.

@DeveloperNicole DeveloperNicole mentioned this issue Feb 25, 2022
Open
@Wilhop
Copy link

Wilhop commented Sep 21, 2022

I should add that:
while --reporters 'cli,json' solves the issue while running locally
We use Azure DevOps CI/CD and we have to specify --reporters cli,json without the quotes in azure-pipelines.yml, otherwise it will lead to an error.

So there are use cases for both without quotes and with quotes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Updated documentation for using multiple reporters DeveloperNicole/newman
3 participants
@DaveMacNeil @palprabhat @Wilhop