Skip to content

JSON export file contains response entries as binary data array, even though it is meant to be JSON or XML #3182

Open
@kriegaex

Description

@kriegaex
  1. Newman Version (can be found via newman -v): 6.0.0
  2. OS details (type, version, and architecture): Linux (Jenkins instance on OpenShift)
  3. Are you using Newman as a library, or via the CLI? CLI after installing via node.js in a Docker container.
  4. Did you encounter this recently, or has this bug always been there: Recently, but actually I never tried to export run results before.
  5. Expected behaviour: I use a command like newman run my_collection.json --environment my_environment.json --reporters cli,json --reporter-json-export test-result.json and the JSON in the export file contains all responses in plain text (XML for SOAP responses, JSON otherwise). Otherwise, I cannot find out what exactly went wrong in my service calls. The responses contain detailed error info. What happens instead, is that in the export file there are lots of response.stream.data arrays.
  6. Command / script used to run Newman: See above, no. 4.
  7. Sample collection, and auxiliary files (minus the sensitive details): This is not specific to any individual collection, it happens always.
  8. Screenshots (if applicable): ---

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