Skip to content
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

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

Open
kriegaex opened this issue Dec 4, 2023 · 1 comment · May be fixed by #3184

Comments

@kriegaex
Copy link

kriegaex commented Dec 4, 2023

  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): ---
@kriegaex kriegaex changed the title JSON export file contains empty response entries JSON export file contains response entries as binary data array, even though it is meant to be JSON or XML Dec 4, 2023
@kriegaex
Copy link
Author

kriegaex commented Dec 4, 2023

Sorry for the initially wrong subject and description, I copied from somewhere and forgot to adjust it. I have just fixed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant