ContributionsMost RecentMost LikesSolutionsKeyboard shortcuts in EditorWhat are the Editor keyboard shortcuts in Mac OS for such things as: Move insertion point to beginning of file Move insertion point to beginning of current line Move insertion point to end of current line Move insertion point to end of file Please note that Mac laptops do not have a Home or an End key, so soapUI should not use either of these in any keyboard shortcut. Thanks, FastBillDEBUG messages in slapUI logEach time I run a TestCase, several DEBUG messages display in my soapUI 4.5.1 log. For example: Thu Jul 19 14:33:22 EDT 2012:DEBUG:Attempt 1 to execute request Thu Jul 19 14:33:22 EDT 2012:DEBUG:Sending request: POST /shopping-ws/services/Shopping/v2 HTTP/1.1 Thu Jul 19 14:33:25 EDT 2012:DEBUG:Receiving response: HTTP/1.1 200 OK Thu Jul 19 14:33:25 EDT 2012:DEBUG:Connection can be kept alive indefinitely Thu Jul 19 14:33:25 EDT 2012:DEBUG:Stale connection check Thu Jul 19 14:33:25 EDT 2012:DEBUG:Attempt 1 to execute request Thu Jul 19 14:33:25 EDT 2012:DEBUG:Sending request: POST /booking-ws/services/Booking/v2 HTTP/1.1 Thu Jul 19 14:33:26 EDT 2012:DEBUG:Receiving response: HTTP/1.1 200 OK Thu Jul 19 14:33:26 EDT 2012:DEBUG:Connection can be kept alive indefinitely Thu Jul 19 14:33:26 EDT 2012:DEBUG:Stale connection check This may be a result of my previously running a Nightly Snapshot build of 4.5.1, but now that I am running the released version I'd like to suppress these DEBUG messages. How/where do I turn them off? Thanks, FastBillProperty Transfer when Source is emptyIn soapUI 4.5.1, I have a Response message in which one ProductCode element looks like this: <ProductCode description="Alpha 1">A1</ProductCode> and another ProductCode which has no value looks like this: <ProductCode description="Other"/> In a Property Transfer step, I have 2 Transfers that transfer these values of ProductCode to two Properties defined in a Property Step. In my subsequent Request messages, I insert the Property value with this type of reference: <ProductCode>$MyProperties#ProductCode1</ProductCode> and later: <ProductCode>$MyProperties#ProductCode2</ProductCode> The first Property Transfer works, correctly transferring the value "A1" to the target Property, and in my subsequent Request messages I have this: <ProductCode>A1</ProductCode> I expected the second Transfer to transfer an empty value to the target Property, and my subsequent Request to look like this: <ProductCode></ProductCode> However, the second Transfer transfers the ProductCode element itself (literally), and it also adds each one of the namespace declarations in my Response message into that ProductCode element. Instead of "", the resulting Property looks like this: <ProductCode description="Other" xmlns="http://..." xmlns:ns2="http://..." xmlns:ns3="http://..." xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"/> As a result, my subsequent Request messages fail. In my Property Transfer, I've tried first setting, then clearing, several of the Transfer options, including: Set null on missing source Ignore empty/missing values The result is always the same. How do I get this Property Transfer to transfer only the empty value of the Source property into the Target property, so that subsequent Request messages that make reference to this property will correctly contain an empty <ProductCode></ProductCode> element? Is this a bug in soapUI?soapUI 4.5.1 on Mac OS -- still missing keyboard shortcuts In the Request and Response editors, shortcut key Command+X ("Cut") still does nothing, although the right-mouse menu "Cut" command does work MOST of the standard Mac OS keyboard shortcut keys for navigation do not work within the Request and Response editors. For example, the standard application shortcut keys for navigation are: * Command+LeftArrow = Move insertion point to beginning of current line * Command+RightArrow = Move insertion point to end of current line * Command+UpArrow = Move insertion point to beginning of first line * Command+DownArrow = Move insertion point to end of last line None of these works as it should. For a complete list of standard Mac OS shortcut keys, please see the "Application and other Mac OS keyboard commands" section of this Apple support page: http://support.apple.com/kb/HT1343Keystroke to save raw requestHi -- For documentation purposes (I write software specs), I often need to save examples of TestStep requests and responses. The Response tab supports Ctrl+S (on Mac, Command+S). However, the Raw view of the request tab does not seem to have any way to save the request that was submitted. I need to save the Raw view of a request, because my XML request contains many references to Properties that would not be helpful in documentation. I don't want to add Groovy scripts to my TestCases to do this, because I only need to save messages once in a while, not every time I submit a request. To save the raw request, I copy the raw XML (from <soapenv:Envelope> through </soapenv:Envelope>, not including the lines at the top above the <soapenv:Envelope> element). I paste the clipboard into my favorite XML editor, and then save the file there. Please add the keyboard shortcut for "Save" to the Raw view of the Request tab. For my purposes, I'd prefer that this Save command include only the raw XML, and omit the lines above <soapenv:Envelope>. Thanks, fastbillRetain Custom Properties tabIn the Properties pane on the left side, below the Navigator, after the user selects the Custom Properties tab it would be very useful for soapUI to remember that selection whenever the user moves to other objects either through the Navigator or by choosing a different message tab in the editor. If the user is inspecting Custom Properties for one object, it is likely that she wants to see Custom Properties for other objects as she navigates through test steps, test cases, test suites, and projects. But soapUI always returns to displaying the built-in properties tab (TestRequest Properties, TestCase Properties, etc.), requiring the user to click "Custom Properties" again each time she navigates to a different object. Thanks, fastbillUnmarshalling ErrorWhen a "Not SOAP Fault" assertion fails, soapUI often returns this response: <soap:Fault> <faultcode>soap:Client</faultcode> <faultstring>Unmarshalling Error: cvc-datatype-valid.1.2.1: '' is not a valid value for 'integer'.</faultstring> </soap:Fault> Unfortunately, it gives no indication where the missing integer occurs in the request message. It would be extremely helpful if soapUI displayed the request line number and character position where it has detected this fault.Re: soapUI 4.5 and loadUI 2.0 released!How could you release version 4.5 with this obvious and very serious regression failure? Our response messages often have more than 10,000 lines of XML. Without Find/Replace, soapUI version 4.5.0 is completely unusable! Please tell us when you will fix this problem. Thanks!Re: On Mac,soapUI Pro 3.6 doesn't follow standard UI conventionsSure...but it's not done with copy-and-paste. In soapUI, you "clone" something that you have in one Project and want in another Project. You can clone an individual Test Step, a Test Case, or an entire Test Suite. In the Navigator pane, right-click the item that you want to clone. You'll find "Clone ..." in the contextual menu. Selecting that will display a dialog box in which you specify the target(s). For example, if you clone a Test Step the dialog box lets you specify the Target Project, Target TestSuite, and Target TestCase (all of which default to the current locations). The default Name is "Copy of xxx" (where "xxx" is the name of the item you are cloning), so you can clone a Test Step within the same Test Case, clone a Test Case within the same Test Suite, etc., without a name conflict. When I clone an item into a different Test Suite or a different Project, I usually remove "Copy of" from the item's Name.Re: On Mac,soapUI Pro 3.6 doesn't follow standard UI conventionsI've been using soapUI since v3.5, and I don't recall ever seeing Undo/Cut/Copy/Paste in any soapUI menu. (This lack of adherence to common UI conventions is probably an oversight on the part of eviware.) However, I have had no problems in v4.0 or v4.0.1 using cmd-x, cmd-c, cmd-v, and cmd-z in request and response messages, property transfer scripts, or Groovy scripts.