Contributions
SoapUI settings - project level proxy
Hi, I do proxy settings on a per-project level in SoapUI. It would be helpful if LoadUI could either: * Use the proxy settings from the SoapUI project, not the overall SoapUI settings file * Allow you to do proxy settings in the SoapUI Runner settings dialog.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0CommentsRe: [Res]Proxy settings at project level for loadtestrunner.bat
After several tests, I have tried these lines in the following locations: * Project TestSuites setup script * Groovy script within test case when the Groovy script is the first step in the test case * Setup script, test case * Setup script, load test case They don't work to set the proxy in any of those locations.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.5KViews0likes0Comments[Res]Proxy settings at project level for loadtestrunner.bat
I need to set proxy host and port AT THE PROJECT LEVEL for loadtestrunner.bat I DO NOT WANT to set the proxy system-wide via File => Preferences => Proxy Preferences. I've tried setting http.proxyHost and http.proxyPort as properties in the LoadTestRunner dialog. They get passed to the command line but when I actually run loadtestrunner.bat they aren't observed. My project-level load test settings are: http.proxyHost=127.0.0.1 http.proxyPort=8888 Any ideas? Thanks.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.9KViews0likes3CommentsRe: [R] New JDBC/Data Connection Data Sources return "clob" data
ResultSet[1]/Row[1]/Column[1] as the Xpath works, but it returns results only for the first row. Is there a way to specify an Xpath to get results for all rows?11 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.4KViews0likes0CommentsRe: [R] New JDBC/Data Connection Data Sources return "clob" data
I need to look for particular XPaths and hand each XML off to a different SOAP request depending on its contents. I have no idea how to do that with more than one row returned from a table at the same time. You can cycle through each row of a DataSource easily within SoapUI; not so much with a JDBC request. My Groovy scripting skills are limited so that's not really an option.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.4KViews0likes0CommentsRe: [R] New JDBC/Data Connection Data Sources return "clob" data
Hi Marcus, I am using SoapUI 4.6.2 and jTDS as a driver. A couple of notes. If I run the same query in a Groovy script within a text editor, I get the same results - Clob objects. Running the query from within a Datasource I created just now in SoapUI 4.5.2 returns Clob objects. A SoapUI DataSource I created several months ago still returns XML for that query. So I believe something recently got pushed to my desktop without my knowledge that caused this. I have not changed jTDS versions and I've ruled out the likely culprit in terms of desktop changes. If I do the call from within a JDBC request step, I get XML results. However, I can't process these results the way I could if a DataSource returned them, so it doesn't do me any good. I'm going to make the recommendation that DataConnection or JDBC DataSources be able to handle Clob objects the same way a JDBC Request test step does.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.4KViews0likes0Comments[R] New JDBC/Data Connection Data Sources return "clob" data
Hi, As of SoapUI 4.6.0 and 4.6.2, my JDBC/Data Connection data sources return data in "clob" format. This data isn't readable unless you handle it with Groovy. When I run exactly the same query in a data source created a few months ago and a data source created yesterday or today, one returns good data and the other (newer) data source returns clob data. This looks like a bug to me.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions5.3KViews0likes8CommentsAccess Datasource values in Datagen step
There is no way to access the Datasource values in a Datagen step. Even if I copy in the context expansions from another step, any script I write with the expansions in a Datagen step returns null. It would be very helpful to have this functionality.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.9KViews0likes1CommentRe: [Resolved] Get rid of unwanted CDATA in request
I developed the answer to my question after reviewing a fair amount of Groovy documentation. The replaceAll method takes a regexp as an argument. The special characters require different handling than if you were using the find method. There are probably more elegant ways to write this but the code scrubs the CDATA enclosure from outgoing requests just fine. matcher = (context.requestContent =~ /<!\[CDATA\[/) context.requestContent = matcher.replaceAll("") matcherdeux = (context.requestContent =~ /\]\]>/) context.requestContent = matcherdeux.replaceAll("") The solution given here on how to strip a CDATA enclosure http://www.soapui.org/Functional-Testing/working-with-cdata.html#6-an-event-handler-to-the-rescue is the one I used in my initial post - the one that didn't work. It would be great if the docs could be updated.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0Comments