Ideally the solution would entail referencing two separate JSON files during a collection run…however, if that’s not possible we could probably bring up a server to host the 2nd JSON payload (or both for that matter) so it could be accessed from a request…is this what you are meaning by the last question in your post? I’d prefer to do it from a local file though.
Right now I’m thinking maybe I could append the ‘expected response’ to the end of the response body in the same JSON file. Then for my tests I could call the responseBody as well as individual .data variables (from the section of the JSON that has the expected response).
I’m not sure if this would work, I’m working on testing it out. Right now, my biggest hang-up has to do with dealing with setting up the request body to happily accept nested JSON structures of varying array lengths from an external file…but I’ve created a separate thread for this: