Koopman_Interna
Contributor
Joined 14 years ago
User Profile
User Widgets
Contributions
Losing my Teststep changes
Hi, I was changing my existing soapUI-tests (I added some JDBC-teststeps and assertions) when suddenly SoapUI reacted strangely. A black screen appeared and disappeared and the changing from one tab to another tab in SoapUI became slow. There were just 3 programs running on my computer and everything seemed normal in my taskmanager. Therefore I saved my project, stopped SoapUI and even restarted my computer. After SoapUI restarted, I couldn't find any of the changes I made. It was like SoapUI never wrote them on my disk. There wasn't even a backup file (the backup preference is activated). Has anybody already had this problem? Or knows what to do about it (besides saving every 5 minutes and hoping that you only lose the changes of the past 5 minutes)? Thanks in advance Kris Uytterhaegen Koopman International2.6KViews0likes2CommentsUnwanted changes inserted by SoapUI Pro
We are using SoapUI Pro (with composite projects) and are using version control to check in our tests. It seems that even when nothing is changed by a user, SoapUI inserts changes into the XML that are noticed by the version control system. Mostly, SoapUI inserts extra id attributes with a uuid, like: id="30938f82-4afa-404f-a25e-fa5f68dee1d0" Just loading and saving a project seems to be enough to trigger this. This happens on settings.xml files, but also on Soap calls, JDBC requests etc. Is there a setting to prevent this, as this is really annoying? Testers now spend a lot of time overviewing their changes and discarding them if they are no real changes. This costs us a lot of time.705Views0likes0CommentsRe: Performance multiple JDBC requests
This gets worse and worse in my daily testing. JDBC calls take up 80 to 90 % of the testing time, and it seems not needed if the connection was not closed every time. Using a soap service to do the same stuff as the direct JDBC statement is checking is way faster. Any news on this?873Views0likes0CommentsTesting for JDBC fault
Hi, For a soap request I can assert that the request is failing by asserting a Soap Fault. I do a lot of DB testing and would like to do the same for a JDBC Fault. But a JDBC request that is in error immediately fails the step, without an assertion. I would want to make that implicit by asserting 'JDBC Fault' or 'Not JDBC fault' To not break old tests the 'Not JDBC Fault' should be included by default? Example: insert into table xxx values (null, null, null) fails for missing required fields. I would like to test that this statement fails.(And thus pass my test). Same for testing ref.integrity constraints. Or delete constraints, where a delete from headertable where id = yyy should fail if there are details referring to it. The test passes if the delete fails.3.2KViews0likes1CommentRe: Using proxy with incorrect content-type
Alas, no luck then. BTW, I was mistaken that the content was xml though. Actual request is like this: POST http://nidxacc:20062/RepeatOrderWeb/___proxy HTTP/1.1 Host: nidxacc:20062 Proxy-Connection: keep-alive Referer: http://nidxacc:20062/RepeatOrderWeb/RepeatOrderDashboard-en_US.html?showToscaErrorCombo=true Content-Length: 886 Origin: http://nidxacc:20062 User-Agent: Mozilla/5.0 (Windows NT 5.1) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/13.0.782.218 Safari/535.1 Content-Type: application/jsonrequest;charset=UTF-8 Accept: */* Accept-Encoding: gzip,deflate,sdch Accept-Language: nl-NL,nl;q=0.8,en-US;q=0.6,en;q=0.4 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: PurchaseOrderEntryLogonCurrentUser=TZU; REPEATORDER_BUYER_LOGON=MST; JSESSIONID=00003j-v5nanjJuV6eS4ncuBBsP:-1 {"uri":"","queryParameters":{},"method":"POST","body":"{\"bindingName\":\"IProductService\",\"method\":\"getProduct\",\"params\":[{\"context\":{\"languageCode\":\"en\",\"defaultLanguageCode\":\"en\",\"mutCallStack\":\"\",\"organizationalUnit\":0,\"userId\":\"\"},\"productIDNumberView\":{\"id\":0,\"productNumber\":\"ABT000010\"}}],\"EGL_PARAMETER_ORDER\":\"request response _return\",\"binding\":{\"type\":\"WebBinding\",\"interfacename\":\"com.koopmanint.purchasing.productmanagement.entities.interfaces.IProductService\",\"name\":\"IProductService\",\"wsdlLocation\":\"wsdl\\\/ProductService.wsdl\",\"wsdlService\":\"ProductServiceService\",\"wsdlPort\":\"ProductService\",\"uri\":\"http:\\\/\\\/nidxacc:20062\\\/PurchasingEntityServices\\\/services\\\/ProductService\"}}","headers":{"EGL_TIMEOUT":120000,"EGLSOAP":"RepeatOrderWeb","Content-Type":"application\/json; charset=UTF-8"}} So it is application/json for the request (where there is no JSON pane for the request, so I have to read the Raw request pane. And the response is: HTTP/1.1 200 Date: Thu, 01 Sep 2011 12:29:58 GMT Server: WebSphere Application Server/7.0 Transfer-Encoding: chunked Content-Type: text/plain; charset=utf-8 Content-Encoding: gzip Content-Language: nl-NL Followed by gibberish because it is zipped. In the HTML tab I see stuff that looks like JSON. But the JSON tab says <Not JSON content>. It starts with: {"headers" : {}, "status" : 200, "statusMessage" :"OK","body" : "{\"result\" : Important point: In the top grid, the columns Interface and Operation are -unknown-. So filtering on operation is not possible for me. Extra point to make: Ctrl-F gives a Find window, but it only searches in the Top grid? I was trying to search in the response, but that did not work.628Views0likes0CommentsUsing proxy with incorrect content-type
Hello, I am trying to use the proxy to see the Soap traffic that our app is generating. The client side code is mostly generated by EGL tools. My problem is that soap requests going from client to server have an incorrect content-type of text/plain (while it should be text/xml). I see the traffic coming by, but I cannot analyse it because the content-type is wrong. I can only see the traffic as 'HTML' where all tags are stripped. XML pane is blank. Is there a workaround for this situation?1.8KViews0likes2CommentsUsability problem in JDBC request
My biggest annoyance in using SoapUI for daily work is the following: When I (re)open a JDBC request page, I can only see 1 line of 56 characters of the SQL request. The SQL request is by far the most important field in this window. If I resize / maximize the window, I can only see 8 lines of 56 characters. I want to see the WHOLE request! Currently I see myself copying the request to the clipboard, paste it into notepad to just SEE the request. And please make a shortcut to Run the request. (And please use this shortcut to run everything that has a green triangle to run...). I really want to be able to use the mouse as little as possible. Maybe you can optimize by giving less space to the params section if there are no params. (I don't use params because I use param substitution directly in my SQL request.)1.7KViews0likes1CommentRe: Drop down boxes are too short
Thanks for the response. Now we are at it, I have some other problems with the Property transfer window: - F2 does not rename - F9 does not clone - I can not reorder transfers (this really is a problem for me) But my biggest problem is: The default size of the window does not show the button to prompt for the XPath expression. I have to resize the window again and again to specify an XPath expression. Please just make it a bit wider by default!1.1KViews0likes0CommentsRe: Remove Empty Content
This is a property of the Soap request (see properties grid for a soap request on the left bottom). I have exactly the same problem. I need an array that does not have any real content in it, to be an actual empty array, not an array with empty elements if all attributes of the elements are empty. Because this might hurt performance, it could be an extra setting "Remove Empty Content recursively", so that empty content is removed until no empty tags exist in the raw request only when this setting is true.5.3KViews0likes0Comments