ContributionsMost RecentMost LikesSolutionsRe: Testsuite runs fine with ReadyAPI but fails with testrunner I didn't and unfortunately SmartBear support is virtually inexistent I am not expecting a solution for this any time soon. Testsuite runs fine with ReadyAPI but fails with testrunner I have a TestSuite in a ReadyAPI project that runs fine in ReadyAPI but keeps failing when running it with testrunner. It does not fail immediately but only around 80% into the test suite and not always fails at the same test. The error information, which you can see below, does not give any useful info. I do not know how to run testrunner in debug mode so at to get any more information on what is failing. This is the only error information shown: at com.smartbear.ready.cmd.runner.SoapUITestCaseRunner.throwFailureException(SoapUITestCaseRunner.java:712) at com.smartbear.ready.cmd.runner.SoapUITestCaseRunner.runRunner(SoapUITestCaseRunner.java:562) at com.smartbear.ready.cmd.runner.pro.SoapUIProTestCaseRunner.runRunner(SoapUIProTestCaseRunner.java:141) at com.smartbear.ready.cmd.runner.AbstractSoapUIRunner.run(AbstractSoapUIRunner.java:333) at com.smartbear.ready.cmd.runner.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:198) at com.smartbear.ready.cmd.runner.pro.SoapUIProTestCaseRunner.init(SoapUIProTestCaseRunner.java:101) at com.smartbear.ready.cmd.runner.pro.SoapUIProTestCaseRunner.main(SoapUIProTestCaseRunner.java:97) Re: Send Binary Data in REST Request I have the same issue, anyone managed a way to do this? Re: using soapUI with Protocol Buffers ? 5 years after this question and no more response from SmartBear, wow Re: Ready API (2.5) opens with a blank screen ReadyAPI 2.6 opens fine. Ready API (2.5) opens with a blank screen Ready API keeps opening with a blank screen. It cannot even be closed after, I have to kill the process. This is on Windows 10 with Ready API 2.5 and I can see the ERROR below in the logs: "Could not initialize class com.teamdev.jxbrowser.chromium.internal.ipc.IPC$a" SolvedSoapUI NG does not check the hostname from the certificate against the CN I have two way SSL setup in my SoapUI NG project (Ready!API 2.0). When I send a SOAP request to endpoint https://server1.com/webservice, that server sends back a certificate which has in the CN server2.com. Shouldn't SoapUI give an ERROR telling that the CN server2.com from the certificate does not match server1.com to which the request was send? How can I setup SoapUI making sure the hostname is checked? What happened to the mock services from my SoapUI Pro project? We renewed our SoapUI Pro Licenses and updated to the latest version of SoapUI Pro. The application is noticably slower but more worrying is that all Mock Services are gone. How can I get them back as we have lots of projects with Mock Services with groovy scripts in them? Re: WS-Security header is not filled by soapUI nmrao wrote: Once you set the credentials at interface level, have selected the endpoing row and clicked on assign? I did just that and now it overwrote the data from one environment on top of the other. Is there a way to do this assignment per environment?WS-Security header is not filled by soapUIHi, I need to add a username and password with wss-paswordtype PasswordText to requests send. When I add this to an individual TestRequest using the TestRequest Properties, all necessary fields are correctly injected in the header. But I do not want to change all the TestRequest Properties of all (al lot!) TestRequests of my project. So I tried adding it using the Interface viewer but when I enter a username and password with wss-paswordtype PasswordText, it is not added to the requests. Same when I enter those fields in the environments interface viewer. Is this a bug or is there another place where I can set this for all requests to a wsdl?