The Burp - Last Test Step Runs Twice when running at the Test Case Level (SOAP)
I'm might be doing something wrong, but when I run my Test Cases (it's data-driven), after the last step (Step [ReadData] ran with status [OK], it runs the last Test Step again. When I run just the Groovy code portion, it's reading the correct # of times (see attachment). Here I've added a couple of log info stmts to show this. I don't have any Setup or Teardown scripts - just the Groovy code and the Request/Response. And yes, the spreadsheet has 6 rows of data and all the input values are different. I have a variable in the SOAP Request and use Assertions - but I just disabled the assertions and it still "burped." Here is my Groovy code: import jxl.* import jxl.write.* import com.eviware.soapui.support.XmlHolder def groovyUtils = new com.eviware.soapui.support.GroovyUtils(context) Workbook workbook = Workbook.getWorkbook(new File("c:\\SoapUIData\\Fahrenheit-Temps.xls")) //The writeable sheet will erase any data, so we can't use the data sheet and update it with the results WritableWorkbook copy = Workbook.createWorkbook(new File("c:\\SoapUIData\\Fahrenheit-Chart.xls"), workbook); WritableSheet sheet1 = copy.createSheet("Fahrenheit to Celsius", 0) Sheet sheet = workbook.getSheet(0) def rowCount = sheet.getRows() for (r=1; r<rowCount; r++){ //r=1 skip header row log.info "Line 13" //Write columns headings Label H1 = new Label(0, 0, "Fahrenheit Value Submitted"); //1st column heading sheet1.addCell(H1); Label H2 = new Label(1, 0, "Expected Result"); //1st column heading sheet1.addCell(H2); Label H3 = new Label(2, 0, "Actual Result"); //1st column heading sheet1.addCell(H3); //Read a Fahrentheit temp valCellContents=sheet.getCell(0,r) cellContents=valCellContents.getContents() FAHRENHEIT = cellContents.toString() testRunner.testCase.setPropertyValue("Fahrenheit",FAHRENHEIT) Label fh = new Label(0, r, FAHRENHEIT); //1st column sheet1.addCell(fh); // Below I'm going to use the properties to perform assertions valCellContents=sheet.getCell(1,r) cellContents=valCellContents.getContents() EXPECTEDRESULT = cellContents.toString() testRunner.testCase.setPropertyValue("EXPECTEDRESULT",EXPECTEDRESULT) Label expectedResult = new Label(1, r, EXPECTEDRESULT); sheet1.addCell(expectedResult); testRunner.runTestStepByName("FahrenheitToCelsius-Request") //Get Celsius temp fromCelsiusValue Response def res = context.expand('${FahrenheitToCelsius-Request#response}') def response = new XmlHolder(res) def CelsiusValue = response.getNodeValue('//m:FahrenheitToCelsiusResult') //Write the actual result in 3rd column Label label = new Label(2, r, CelsiusValue); //3rd column sheet1.addCell(label); } //Gets next row log.info "Line 51" copy.write(); copy.close(); workbook.close() Here is the Soap Request: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tem="http://webservices.daehosting.com/temperature"> <soapenv:Header/> <soapenv:Body> <tem:FahrenheitToCelsius> <tem:nFahrenheit>${#TestCase#Fahrenheit}</tem:nFahrenheit> </tem:FahrenheitToCelsius> </soapenv:Body> </soapenv:Envelope> Thanks in advance.
LoadUI Results with Data Driven Tests Questions
Hi, I am currently using SoapUI NG Pro and LoadUI (not Pro) through Ready! API 1.1.0. I have setup a very simple data driven test that calls a service repeatedly with different values (read from an Excel file). In order to see how it works, I ran the test as a Simple Strategy with 1 Thread and a Limit of 1 Total Run. The results shownon the Test Step calling the web service as: Count = 71 (this is the correct # of rows in my input file) Min = 43 Max = 43 Avg = 43.19 Last = 43 The results returned on the overall Test Case was: Count = 1 Min = 3099 (this appears to be the total time it took the thread to complete all 71 runs + the 46ms it took to load the data source) Max = 3099 Avg = 3099 Last = 3099 It appears to me that the timing (min & max) results for the Test Step are displaying as the average time of all of the runs in that thread. For example, if I had only 2 runs of the test steps in that data driven test with the times of 10ms and 400ms, the min and max would show as 205ms. Questions: Is my observation correct that each thread only reports an average result of the test step runs? Is it possible to have the data driven results more accurately represented (maybe I don't have an appropriate option selected)? Instead of my example where 205ms was displayed in both min & max, could it show 10ms for min and 400ms for max?