edhedh
15 years agoOccasional Contributor
Datasource's first row not ignored, although it should
I'm preparing my load tests. I'm using SOAPUI Pro 3.5.1
I've got the same problem as mentioned in viewtopic.php?f=13&t=5971#p18683
Has this bug been fixed in SOAPUI PRO ? If yes, as off which version ?
If not, is there a workaround.
This is really a showstopper for me and having a negative impact on our project plan and preventing to finish our loadtest in time.
Please advise.
Thanks,
EDH
Problem description (taken from mentioned thread):
I have set up a web service test with a file datasource getting its input from a CSV file.
The CSV file contains the headings in the first column to be self-explanatory.
To ignore the heading, I have to set "start row" to "1".
When I feed this datasource with standard settings, it works.
However, I'm building a load test, so I want to share this datasource across threads.
When I enable the "shared datasource" option, soapUI no longer ignores the first row, but starts at line 0, failing the test.
This is reproducable and happens on every run.
As soon as I disable the "shared datasource" option again, it works.
I've got the same problem as mentioned in viewtopic.php?f=13&t=5971#p18683
Has this bug been fixed in SOAPUI PRO ? If yes, as off which version ?
If not, is there a workaround.
This is really a showstopper for me and having a negative impact on our project plan and preventing to finish our loadtest in time.
Please advise.
Thanks,
EDH
Problem description (taken from mentioned thread):
I have set up a web service test with a file datasource getting its input from a CSV file.
The CSV file contains the headings in the first column to be self-explanatory.
To ignore the heading, I have to set "start row" to "1".
When I feed this datasource with standard settings, it works.
However, I'm building a load test, so I want to share this datasource across threads.
When I enable the "shared datasource" option, soapUI no longer ignores the first row, but starts at line 0, failing the test.
This is reproducable and happens on every run.
As soon as I disable the "shared datasource" option again, it works.