CSV File with Quotes Parsed Correctly in Collection Runner, but not in Newman

1. Newman Version (can be found via newman -v): 4.5.5
2. OS details (type, version, and architecture): Windows 10 x64
3. Are you using Newman as a library, or via the CLI? CLI
4. Expected behaviour: CSV file be parsed correctly, as it is in the postman collection runner
5. Command / script used to run Newman: newman run “$collection” -e “$environment” --folder “Default” -d $pathToTestData + “Default.csv” -r $reportType

I can do a collection run with no issues in the collection runner, however when doing the same collection run in newman, an error message will be thrown. The issue appears to be a difference in the way the csv file is parsed in newman vs in the collection runner. The csv file contains multi line values, as well as values that contain double quote characters.

It seems that the collection runner correctly escapes the commas before running while newman does not. Here is an example showing the preview data window in the collection runner:

Here is a look at the raw text of the same csv file:

Steps to reproduce

1. Create a csv file that includes double quotes
2. Pass in the csv file to newman via the -d option
3. Attempt to run this newman command
4. Get the following error message: error: Invalid Closing Quote: got “”" at line 2 instead of delimiter, row delimiter, trimable character (if activated) or comment

[SimonVHB]

@codenirvana I’m getting a similar error: error: Invalid opening quote at line 2

The csv datafile that I’m using looks like this: It only has one double quote (in comparison to """ like the problem above)

I can’t figure out how to work around this problem (untill v5 is released). How do I escape the quotes for it to work?

[iheartdaikaiju]

@SimonVHB I was able to verify if you do “[”“5dd…427"”]" That will work in the Collection Runner in Postman, which I feel should be the recommended alternative, rather than \" which is not part of RFC 4180