newman -v): 3.8.3 or 3.10.0
@SowmyaT Are you facing this issue in both 3.8.3 & 3.10.0?
Also, can you share the following details, to help reproduce the bug:
newman.runYes @codenirvana , Am facing this issue in both 3.8.3 & 3.10.0.
newman.run only like,newman.run({
reporters: ['cli', 'junit'],
collection: "Examples.postman_collection.json",
disableUnicode: true,
noColor: true
});
@codenirvana , Any Update on this.. Please let me know.
@SowmyaT I tried to reproduce the issue using the same options you provided.
disableUnicode is working fine for me, but I do see there's some problem with noColor.
I need to investigate further to pinpoint the issue, will update you once it is fixed.
@codenirvana , We couldn't find this is the newman or node or OS version issue. And we don't need to use disableUnicode & noColor. Also we updated the latest node versions as v8.11.3 and tried, still facing the same issue.
And If we running that same node js file in command line, It is working fine for us. We are executing & storing the report into the html file using file-system.. That time only we are getting this Unicode chars issue. [NOTE]
The same below library options worked fine earlier in that same Mac OS:
newman.run({
reporters: ['cli', 'junit'],
collection: "Examples.postman_collection.json"
});

Output should be like the above without giving the disableUnicode as earlier. Please fix this asap.
@codenirvana , What is the status of this issue.. Kindly let me know.
@SowmyaT a fix has been added in #1653 which will be rolled out with the v4 release.
You can test this using v4.0.0-beta.2.
The color option is updated, you can check the updated API Reference here.
For your use case, try using:
newman.run({
reporters: ['cli', 'junit'],
collection: 'collection.json',
disableUnicode: true,
color: 'off'
});
Let me know if the issue still persists.
@codenirvana . Thanks for the Update! After installed the latest version 4.0.0-beta.2.. Its works fine now.
@SowmyaT This has been fixed in Newman v4.0.0.
Most helpful comment
@SowmyaT a fix has been added in #1653 which will be rolled out with the
v4release.You can test this using v4.0.0-beta.2.
The color option is updated, you can check the updated API Reference here.
For your use case, try using:
Let me know if the issue still persists.