When parsing the postman-samples results (from standard documentation) the two POST examples have "undefined" appended to the end of the step description.
Expected Behavior
"undefined" values should not be appended to step description
Current Behavior
Test steps for non-assertions have 'undefined' appended when testCase.body is undefined.
Possible Solution
Only append value of testCase.body after testing for undefined value.
Steps to Reproduce (for bugs)
Copy postman-samples from documentation
Set up Launch agent to deliver Postman results to Pulse trigger linked to PostmanJSON action.
Use 'Run now' agent option to run newman command to generate JSON results for tests copies to c:\postman-samples
Here's what the result looks like in qTest:
Context
Discovered while verifying Launch Postman JSON parser delivers results comparable to Pulse Postman JSON parser.
When parsing the postman-samples results (from standard documentation) the two POST examples have "undefined" appended to the end of the step description.
Expected Behavior
"undefined" values should not be appended to step description
Current Behavior
Test steps for non-assertions have 'undefined' appended when testCase.body is undefined.
Possible Solution
Only append value of testCase.body after testing for undefined value.
Steps to Reproduce (for bugs)
Context
Discovered while verifying Launch Postman JSON parser delivers results comparable to Pulse Postman JSON parser.
Your Environment