Forum Discussion
richie
4 years agoCommunity Hero
Hey smpa01,
Apologies, i thought id already answered this.
I can suggest two options....1 is totally overkill but it does give you what you need and more but the other option also its a bit awkward as you have to do it for each request. Also im unsure how it handles loops.
The overkill option (that i know handles loops) is using an event handler and you have a simple script that writes out the requests and responses (i use it to archive my test evidence). Advantage of this is that you only have to create one event handler script and it does all the work writing to a specific directory the inputs and outputs for each teststep.
The other option: double click the request to the navigator frame to view the request's properties. The Dump File property is the one you need.
Ta
Rich
Apologies, i thought id already answered this.
I can suggest two options....1 is totally overkill but it does give you what you need and more but the other option also its a bit awkward as you have to do it for each request. Also im unsure how it handles loops.
The overkill option (that i know handles loops) is using an event handler and you have a simple script that writes out the requests and responses (i use it to archive my test evidence). Advantage of this is that you only have to create one event handler script and it does all the work writing to a specific directory the inputs and outputs for each teststep.
The other option: double click the request to the navigator frame to view the request's properties. The Dump File property is the one you need.
Ta
Rich
- smpa014 years agoNew Contributor
Hi richie
Thanks for looking into this. It is resolved here https://stackoverflow.com/questions/65103126/datasink-step-to-return-each-response-with-all-the-children
Thanks
Related Content
- 2 years ago
Recent Discussions
- 10 days ago