-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Newman could not find "cli junit" reporter #2205
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.
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
Comments
I was having the same issue earlier while trying to use |
@palprabhat Huh, yea that did it for me too. Newman needs updated documentation. |
I should add that: So there are use cases for both without quotes and with quotes. |
It's funny, locally I don't need the quotes, but I need them on Azure Devops. Both are Windows. Tested it with 6.2.1
See #3304 |
newman -v
): 4.5.7 & 4.5.6 (failing on both)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
The pipeline

Newman installed on the machine

The reporter

Steps to reproduce the problem:
-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.
The text was updated successfully, but these errors were encountered: