Forum Discussion
SmartBear_Suppo
Alumni
17 years agoHi AnB,
Indeed, you can and should use DataSink to store the results (i.e. parts of the response) of your Requests to an Excel file.
You need to add a DataSink test step (e.g. SaveToExcelDataSink) between Request and DataSourceLoop test steps. Then you need to define properties and use context menu (right click) to access "Get Data..." menu to select from the source value for each property.
Make sure the output Excel file already exists. I just discovered a bug manifesting when Excel DataSink output file does not exist and which will most probably be fixed in the next version.
If you need to extract node elements from an XML-structured SOAP body of your Request, the best way to do this is via a Property Transfer data step (which you would put between your Request and SaveToExcelDataSink test steps).
Do let is know if you have made a step forward or if you need more help.
Cheers!
/Nenad Nikolic a.k.a. Shonzilla
Indeed, you can and should use DataSink to store the results (i.e. parts of the response) of your Requests to an Excel file.
You need to add a DataSink test step (e.g. SaveToExcelDataSink) between Request and DataSourceLoop test steps. Then you need to define properties and use context menu (right click) to access "Get Data..." menu to select from the source value for each property.
Make sure the output Excel file already exists. I just discovered a bug manifesting when Excel DataSink output file does not exist and which will most probably be fixed in the next version.
If you need to extract node elements from an XML-structured SOAP body of your Request, the best way to do this is via a Property Transfer data step (which you would put between your Request and SaveToExcelDataSink test steps).
Do let is know if you have made a step forward or if you need more help.
Cheers!
/Nenad Nikolic a.k.a. Shonzilla