Passing JSON from itest into python command
I have a device returning perfectly valid JSON, however when it seems to get grabbed by ITEST it escapes it and miss format it.
I basically just want to save a json response and pass it into a python session, What is the best way to do this? I was dealing with the escape characters by just using .replace but now for some reason not only is there \ on every " it randomly throws in {} which cant be fixed with .replace.
Is there just a simple escape method I can just use on the variable when passing python the argument?
Thanks in advance.
Seems like I just need to escape new lines, not sure how thats done in itest.
In order to save the JSON output only, you will need to use "Store only the value of the response" from Step Properties / Other Post-processing / Store Response.
I did a similar test with and without the checkbox, and it is saving the correct JSON (when option is checked)
What Python version do you use? And can you send some screenshots?
Latest python, the issue seems to be when using Curl and storing the response, in compresses it down and enforces the restrictions of the box, so for example without even touching the data and purely just writing to file using the itest write to file, it looks like this.
Adds in white space at the end and splits up closing "'s
Also, when I save the valid response to a variable and pass it to python, it throws an error exactly at "goplenState which just so happens to be the start of the new line. If I read this file (written file) in a external python script and run regex to remove all white spaces and new lines, it becomes valid json again. So its purely the format side, but ideally we would want to avoid running a external script on this.
Not sure why curl or itest is basically taking this valid json and forcing it into some width requirement.
Hi @WillUK,
Please file a new Spirent Support case on CSC so that we can proceed with scheduling a debug call. This would help speeding the things up in order to achieve a faster resolution.
Once the issue is fixed I will reply to this thread with the accepted solution.
Thanks,
Bogdan
