question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Invalid opening quote at line 3

See original GitHub issue
  1. Newman Version (can be found via newman -v): 3.8.0
  2. OS details (type, version, and architecture): Microsoft Windows [Version 10.0.15063], AMD64
  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: Have only recently tried
  5. Expected behaviour: Newman should parse the JSON data file successfully
  6. Command / script used to run Newman: newman run “xxxx.postman_collection.json” -n 3 --f testFolder -e xxxx.postman_environment.json -d “TestData.json” --ssl-client-cert xxxx.crt --ssl-client-key xxxx.key --ssl-client-passphrase xxxx
  7. Sample collection, and auxilliary files (minus the sensitive details):

TestData.json [ { “Iteration”: 1, “expectedResponseCode”: 200, “expectedAppResCode”: 0, “expectedErrMessage”: “” }, { “Iteration”: 2, “expectedResponseCode”: 200, “expectedAppResCode”: 0, “expectedErrMessage”: “” }, { “Iteration”: 3, “expectedResponseCode”: 400, “expectedAppResCode”: 3004, “expectedErrMessage”: “Access token is invalid or expired.” } ] 7. Screenshots (if applicable): output: Invalid opening quote at line 3

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:13 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
porterfccommented, May 1, 2018

I had the same problem, the csv data file worked in Postman but not in Newman. To resolve the issue, after saving the file from Excel I replace all double double quotes “” with backslash double quote \"

1reaction
amnomancommented, Sep 29, 2017

After updating to v3.8.3-beta.1 it’s working fine. Thanks 😃

Read more comments on GitHub >

github_iconTop Results From Across the Web

csv-parse is throwing Invalid Opening Quote - Stack Overflow
Invalid Opening Quote: a quote is found inside a field at line 2. The quote is not an opening. It's technically a closing....
Read more >
Opening line quote error #139 - adaltas/node-csv-parse - GitHub
I get Error "Invalid opening quote at line #{@lines+1}" when trying to parse a CSV that has quotes around it's first value in...
Read more >
Imported CSV, getting Invalid opening quote
Your macro command is ok. The error “Invalid opening quote” means that a inside the CSV file something is wrong, probably a missing...
Read more >
Errors - CSV Parse
Thrown when the parsing of data end while an opening quote is not closed. API Errors. code: CSV_INVALID_ARGUMENT message: Invalid argument: got {value}...
Read more >
Solutions to common product CSV import problems
Another possible cause is an extra quote that has been added to the file. Open the file in a text editor and find...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found