ContributionsMost RecentMost LikesSolutionsRe: Ready API 3.50.0 Regression Issue: Test Case Halts when SOAP Fault occurs Hi, This is probably a ticket for SmartBears helpdesk, rather than a community forum. If you're using ReadyAPI, then you have access to support. Regards, Chris Re: Detailed Reports Hi, Sorry, I'm away for two weeks, so I cannot provide a detailed solution. Firstly though, take a look at data sinks. These are the opposite of datasources and allow you to write details of a loop iteration to csv, text file, whatever. Re: Detailed Reports Hi, It sounds like data-driven tests have become your new best friend. I use these extensively, though in my data source, I have the values and expected results in each row. Not two different data sources. I don't use assertions/smart assertions in my data driven test as I want the test to continue to the very end so I can see all the failures, instead of the test failing after the first assertion fail. Instead I write groovy scripts to run for each iteration to check actual against expected and return the result of the check. At the end of end iteration, I then write to a data-sink step. This step will report values from the datasource and the results of the above groovy scripts. Then, once the test is complete, I can use Excel to review all the results. Re: Executing test case loop multiple times Hi, A simple, but might not be the best, is an 'outer' data source loop. Create a new Excel spreadsheet with a 'iteration' column with four rows. E.g. 1,2,3,4. This is your "configurable number of times loop". Before your original Data Source step, create a new Data Source Step called something like 'Outer loop', that links to the new spreadsheet. Finally, create a new Data Source loop that links back to the new 'outer' data source. Re: Mismatch between response from a CURL request and ReadyAPI response In ReadyAPI, you show a screenshot of the request, after you have clicked 'Send' and got the response, have a look at the Raw tab next to the Request tab. The contents of the raw tab show exactly what ReadyAPI passed to the service, but it is only populated after Send is clicked. You might be able to spot what is different by comparing Raw request to your Curl request. In ReadyAPI, it looks like you're passing {id}, could that be the difference? Re: readyapi groovy script library In your script, wherever you see project.getContext().report.getTestSuiteResultList() try log.info(project.getContext().report); or log.info(project.getContext().report.getClass()); SOmething like that may give you the full class name so you can look in the guide Re: readyapi groovy script library The ReadyAPI/SoapUI Classes are actually Java, not Groovy. Pedantic comment out of the way, try here... https://www.soapui.org/apidocs/5.5.0/index.html?com/eviware/soapui/support/components/package-summary.html Re: Boolean check Hi, The use case is from a previous question... https://community.smartbear.com/discussions/readyapi-questions/assertions/262648/Assertions | SmartBear Community In ArmyGrads Groovy snippet, the assertion isn't required for the use case. But I can see why Rao added it for his demo to show that the value can be found. For ArmyGrads example to work, you need use Get Data to pull in the required value from the datasource step and assign it the var datasourceBook1 prior to the IF statement. Something like... def datasourceBook1 = context.expand( '${CustomerDataSource#Book1}' ); Then you should both the response value and datasource values. Re: Boolean check Hi, The result in quotes was part of a solution from another Q last week. The Groovy check returns a String, which in turn is persisted in a Datasink step. This part of the solution was not to assert as fail stops the test. Instead, this part was to report all passes and fails. Re: Assertions Me neither! Just a tester who's picked this up along the way! I'm glad I was able to help though.