Skip to content

Newman could not find "cli junit" reporterΒ #2205

@DaveMacNeil

Description

@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
    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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions