JUnit-parameterized vs. SoapUI-DataSource-loop
How to get SoapUI-JUnit-style reports to include a testcase per each loop over a datasource?
Specifically, this is on the subject of the granularity of unittest-like reports -
1) Disregarding SoapUI, if I create a JUnit-test with a single test-method, I parameterize this test with annotation. If I have a set of parameters, the test-method is invoked for each parameter and the resulting JUnit-report includes output per each invocation/each parameter.
2) In the context of SoapUI (Pro), I can create a testcase with a sequence of teststeps which reads some parameters from a DataSource, invokes a webservice with a request with some properties from the DataSource, and makes a DataSource-Loop. The SoapUI JUnit-style-report has a single testcase, but no information specific for each (SOAP-)invocation/each iteration.
In SoapUI, how do I get the effect of a testcase in the JUnit-style-report for _each_ individual iteration over some data? -Comparable to plain JUnit-parameterization.
Specifically, this is on the subject of the granularity of unittest-like reports -
1) Disregarding SoapUI, if I create a JUnit-test with a single test-method, I parameterize this test with annotation. If I have a set of parameters, the test-method is invoked for each parameter and the resulting JUnit-report includes output per each invocation/each parameter.
2) In the context of SoapUI (Pro), I can create a testcase with a sequence of teststeps which reads some parameters from a DataSource, invokes a webservice with a request with some properties from the DataSource, and makes a DataSource-Loop. The SoapUI JUnit-style-report has a single testcase, but no information specific for each (SOAP-)invocation/each iteration.
In SoapUI, how do I get the effect of a testcase in the JUnit-style-report for _each_ individual iteration over some data? -Comparable to plain JUnit-parameterization.