mwalter
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: How to update a JSON request body
Hi, Currently, we don't have any of this test using Groovy. I understand what most examples are doing, but I'm not exactly fluid in Groovy yet (I've done a couple of simple XML-based events). The JsonBuilder sounds like it might be a possible solution but I'm not familiar with how it works or exactly how it would be implemented. Is there any good doc on that or a site you know of with good explanation? Thanks, Mike6.5KViews0likes0CommentsHow to update a JSON request body
Hi, I'm trying to update part of a Json REST request. Below is the json in question and I need to update the last row (OpenTaxFilters) to add values. I haven't really seen anything out there that anyone has done equivalent to this, but I'm expecting it must have been done. Anyone have any ideas on how I could go about this? "GetOpenTaxLotsByAccount": { "AccountNumber": "54007070", "SecurityNumber": "", "PriceIndicator": "", "OpenTaxFilters": {"HeldAwayIn": ""} Thanks, Mike6.6KViews0likes5CommentsLooking for help on how to use xpath match to verify an empty node
Hi, I have the following output of a JDBC query that I need to confirm the value in <_3></_3>, basically the data is the second line of an address. When there is a value in the second line of the address, everything is fine but when there is only one line to the address and the second line is blank it comes back as below. I'm trying to figure out how to configure the Expected Result in the Xpath Assertion for that value. If I leave the Expected Result field blank, I suspect that everything will pass and it's not checking anything. Null isn't correct either. Need some thoughts on how to verify that no data comes back in that line. Thanks in advance for any help/ideas. <Results> <ResultSet fetchSize="64"> <Row rowNumber="1"> <_2>450 N. SUNNYSLOPE RD.</_2> <_3/> <_4>BROOKFIELD</_4> </Row>857Views0likes1CommentProject disappears when I try to open it
Putting this out there to see if anyone else has seen similar behavior or has a solution I can try. For a while now I've noticed that at times when I double-click a closed project to open it (in the SoapUI NG tab), the project folder just poof disappears. I suspect this might have something to do with having ReadyAPI open when I undock my laptop and am disconnected from the company network. It's just annoying at this point, but anyone have any ideas how to fix the disappearing act? Thanks, Mike879Views0likes0CommentsRe: How to reference an Environment property from the custom headers of a request
dg3781, Yes, that actually does help and works well. So thank you for that. It still baffles me why the original solution stopped working. My initial thought was that something changed with the 1.9.0 version because I did upgrade in between these 2 attempts but whatever, after I applied your change my script started working again.3.2KViews0likes0CommentsSetting to turn off nil="true" in form view?
Hello, I have a problem that seems similar to SOAP-2517 but I don't know what the resolution of that issue is or if it even really solves my problem. We've noticed when working on recent projects that when using form view, if we leave a nillable element blank, SoapUI adds a namespace to the element and sets it to nil (part in red is added by SoapUI). <v11:SortBy xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/> The problem is that this is causing our requests to fail, as the backend is not expecting this and is faulting. Is there a setting in SoapUI where we can control whether the tools adds this information or not? Without it, the form view (which is a key selling point) is somewhat useless to us. Thanks, Mike769Views0likes0CommentsRe: How to reference an Environment property from the custom headers of a request
Hi dg3781, Here's what worked for me. Looking at you code vs what I did your change might be as simple as quotes around the environment property. See if this works for you. def headers = request.requestHeaders headers.remove("FirmId") headers.put( "FirmId", "${#Project#FirmId}" ) request.requestHeaders = headers5KViews0likes5CommentsSoap request form view not working in ReadyAPI 1.9
Has anyone else seen this problem or have a solution? I recently downloaded the 1.9 version of ReadyAPI and in SoapUI NG, when I go to one of my existing SOAP requests, I'm getting a message in the form view: Warning: The request is too large of complex to show in the Form editor. The problem with this is that the SOAP request is not large or complex, and the Form view for this same request worked fine in v. 1.8.5. I've included screenshots of what I'm encountering.Solved1.7KViews0likes1Comment