Contributions
Re: [Res] Can't run imported groovy step in LoadUI
Thanks for your help. It's running now. I think you must be right that it's a config problem. I didn't make any changes to code or script, but I made some config changes to make it run better in SoapUI load test. After those changes, it works in LoadUI. The project you gave me ran without issue also, so I think whatever the problem was is now fixed for everything. Thanks again.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2KViews0likes0CommentsRe: [Res] Can't run imported groovy step in LoadUI
Thanks for responding. Switching the jar causes LoadUI to fail to open. I tried changing the name to groovy-all-1.8.5.jar in case it was just looking for a filename, but that didn't work. Versions: LoadUI Pro = 2.8.1, Build version = 2014/11/13, groovy-all-1.8.5.jar SoapUI Pro = 5.1.2, Build Date = 20140904-1426, groovy-all-2.1.7.jar10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2KViews0likes0Comments[Res] Can't run imported groovy step in LoadUI
I have a test that works fine in SoapUI pro. I imported it into a trial version of LoadUI pro. It fails on a groovy step when I do run once. Nothing is printed to the table log, and I don't know where to go to get the error. .loadui/logs/soapui.log shows no errors, and .loadui/logs/soapui-errors.log is empty. The groovy is super simple: def startMillis = System.currentTimeMillis() context.startMillis = startMillis10 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.2KViews0likes4CommentsAccess url with basic authentication in Rest Discovery
I'm not able to access a url that uses basic authentication when using the internal browser. I tried https://username:password@myurl.com , but that didn't work. Is there any way to supply username and password for basic authentication?10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1KViews0likes1CommentSupport for WebSockets
This is probably a major project to tackle, but WebSockets are becoming a pretty common protocol. It's a totally different paradigm from other supported HTTP protocols, so I know that it would be difficult to integrate into SoapUI. The ability to open a connection, do the initial handshake, and send messages back and forth would be a good start. Ideally, I would like to be able to create a test case that can have an open webSocket connection and test steps to send/receive messages over that connection. It would also be nice to eventually have some load testing, duplex messages, mocks, and recording. Basically, similar support to what exists for SOAP and REST.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions3.8KViews0likes3CommentsSupport for HTTPS in rest discovery proxy
It would be nice if it were possible to record https traffic using the external proxy in rest discovery. I realize that the internal browser gives you that, but there are a lot more options if you can use a modern browser like Chrome or Firefox.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes1CommentRe: Disable websockets in rest discovery internal browser?
That didn't work for me. Steps I took: 1 - Went to web app without using the proxy 2 - Exported certs from browser. There were 3 levels 3 - Used keytool to import certs to cacerts keystore. Root level cert already existed. The other 2 were imported successfully 4 - Configured browser to use localhost:8081 proxy for http and ssl (tried on firefox and chrome) 5 - Tried to navigate to https web app. Result: Web page never loads. Eventually it times out. Chrome give the error ERR_TIMED_OUT. If I try to reload the page, I get ERR_TUNNEL_CONNECTION_FAILED.10 years agoPlace ReadyAPI QuestionsReadyAPI Questions957Views0likes0CommentsDisable websockets in rest discovery internal browser?
Our application supports websockets and long polling. If the client supports websockets then it uses that, otherwise it defaults to long polling. Because SoapUI doesn't support websockets, I would like to record a test using long polling. Unfortunately, I'm stuck. I would disable websockets in firefox and use the proxy, but the app is https and that's not supported. I would use the internal browser, but it's using websockets and not recording any traffic. Is there any way to disable websockets in the internal browser like you can in firefox? Is there any other path that I'm not thinking of?10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes2Comments- 10 years agoPlace ReadyAPI QuestionsReadyAPI Questions872Views0likes0Comments
[Res] REST Discovery extremely slow
We're having a lot of difficulty using REST Discovery. While recording, the SoapUI app seems to get bogged down after only a few calls. This causes everything in the app to be frozen while it tries to catch up on recorded requests. I don't mean a little bit of lag. It's taking 30 minutes or more to record 10 or 15 requests. We're using pro 5.1.1, and we've tried multiple websites including our own and soapui.org, both mac and windows, both internal browser and proxy with firefox. Nothing seems to work. Is there anything we can do? CPU/memory doesn't seem to be spiking very high, but is there any configurations we should change?10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes2Comments