Newman: Newman could not find "cli junit" reporter

[DaveMacNeil]

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
  

• Newman installed on the machine
  

• The reporter
  

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]

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]

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