- SOATest Automation Scale Up with Data Source
Comments
-
Data sources are loaded into memory at the start of test execution, before the first test executes. This could include data read from a CSV or Excel file on disk. So, the size of your data source should not impact test execution, aside from some small, typically imperceptible amount of time while data source row/column data is being loaded into memory from the disk.
Your data source can be as large as you like as long as enough memory is available. However, if for some reason SOAtest runs out of memory then you can allocate more as described here. Certain data source formats like Excel also have their own limits on numbers of columns and rows as described here.
1 -
Thank you @benken_parasoft
0 -
Is there an option to write couple of fields extracted from response via Json/XML Data Bank to against the respective data rows ?
0 -
Data sources are used to make tests cases loop, row-by-row, where each iteration uses a different row. So, you would need to make sure the row for that particular test invocation also contains the data you wish to use for validation. In other words, your data source could have some columns containing data you send in the request and other columns containing the data you want to verify in the response.
0 -
If you need a validate fields using values in your data source, you can use a JSON/XML Assertor and configure the expected value to point to a column from your data source.
0 -
I need to extract values from response to verify elsewhere ,,, for Example My Request creates and application (with application ID) using the customer data fed from a data sheet and Application ID from the response need to be extracted and written in a Excel file...
0 -
SOAtest does not have built-in ability to write extracted values to Excel - you would have to write code to do that yourself. However, using an XML or JSON Data Bank, you can store the values to be used later - use either the custom column option or the Writable Data Source to store values to use later.
1