-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Closed
Description
- Newman Version (can be found via
newman -v
): 4.5.7 & 4.5.6 (failing on both) - OS details (type, version, and architecture): Windows 10 Pro v.1803 OS Build 17134.765
- Are you using Newman as a library, or via the CLI? CLI
- Did you encounter this recently, or has this bug always been there: Recently (Started in builds Dec 30th.)
- Expected behaviour: Newman to run and publish results via Junit
- 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
- Sample collection, and auxiliary files (minus the sensitive details):
- Screenshots (if applicable):
Steps to reproduce the problem:
- Install newman globally
- 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.
304NotModified
Metadata
Metadata
Assignees
Labels
No labels