When using Newman with the JSON reporter, it seems that the section 'run->execution' contains invalid items.
I created a Postman collection with one request (for instance, GET http://example.com) and added a pre-request script for this request. In this script, 'pm.sendRequest' was added with the second request (for instance, POST https://postman-echo.com/post). This collection was exported and run by Newman (command line: newman run test_01.json -r cli,json).
In the report file, within the section 'run->execution', there are two sections, and these sections are completely equal with information about the last request-response 'GET'. I would expect the section to contain two different responses, 'POST' and 'GET'.
Newman Version (can be found via newman -v): 6.1.2
OS details (type, version, and architecture): Windows 11
Are you using Newman as a library, or via the CLI? Newman via CLI
Did you encounter this recently, or has this bug always been there:
Expected behaviour: I would expect the json section run->execution contains different responses
Command / script used to run Newman: newman run test_01.json -r cli,json
When using Newman with the JSON reporter, it seems that the section 'run->execution' contains invalid items.
I created a Postman collection with one request (for instance, GET http://example.com) and added a pre-request script for this request. In this script, 'pm.sendRequest' was added with the second request (for instance, POST https://postman-echo.com/post). This collection was exported and run by Newman (command line: newman run test_01.json -r cli,json).
In the report file, within the section 'run->execution', there are two sections, and these sections are completely equal with information about the last request-response 'GET'. I would expect the section to contain two different responses, 'POST' and 'GET'.
Newman Version (can be found via newman -v): 6.1.2 OS details (type, version, and architecture): Windows 11 Are you using Newman as a library, or via the CLI? Newman via CLI Did you encounter this recently, or has this bug always been there: Expected behaviour: I would expect the json section run->execution contains different responses Command / script used to run Newman: newman run test_01.json -r cli,json