btmuc
New Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Groovy Editor Annoyance
Hi, two weird properties of the Groovy Editor that (IMHO) should be improved: 1. Changing the font size and / or font type in the 'Editor Settings' tab of the Preferences dialog only affects ordinary text. Any highlighted portion keeps its initial size and font type. 2. Indentation is hardwired to 5 characters. This is a very uncommon setting. 4 or 8 are far more common (or even 2 or 3). This should be another setting configurable by the user. Cheers949Views0likes0CommentsRe: Data drive from csv in SoapUI Free version
Data driven testing is one of the features that distinguishes SoapUI Pro from the the Open Source version. So don't expect any confortable support of data driven testing in the Open Source version. The only work-around I could think of was to invoke the test case from a script (Groovy or shell script). This scripts handles the interation over some data source and transfers the data to the test case in a properties file. The name of this property file is specified via the system property soapui.properties.730Views0likes0CommentsRe: property expansion in mocked responses
Hi Ole, yes, I'm talking about SOAP Mock Response test steps. I've just double-checked: Putting <cus:TransactionId>${#TestCase#TransactionId}</cus:TransactionId> in the XML of the response of a Mock Response test step yields <cus:TransactionId></cus:TransactionId> As a work-around I've used this line in the script of the Mock Response test step context.setProperty('TransactionId',context.testCase.getPropertyValue('TransactionId')) and modified the above XML code to <cus:TransactionId>${TransactionId}</cus:TransactionId> This yields <cus:TransactionId>D0780100027579</cus:TransactionId> Thus I know that the test case property 'TransactionId' has been properly set. Perhaps I've hit a bug. I'm using 3.6.1 Open Source Edition. Cheers M1.3KViews1like1Commentproperty expansion in mocked responses
Hello, after having read http://www.soapui.org/Getting-Started/m ... ponse.html I tried to use property expansion like ${#TestCase#TransactionId} for a mocked response. This test case property has been set in the test case' setup script and successfully referenced in a SOAP request test step. But for the mocked response this expression yields an empty string. So my question: Is property expansion possible in the same way as for SOAP request steps, e.g. using ${#TestCase#TransactionId}? Or is it only possible to use 'simple' properties like ${TransactionId}? Thanks in advance M1.7KViews0likes3Comments