Contributions
- 7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.2KViews0likes0Comments
Re: Shutdown Test Case Runner and all ReadyAPI / SoapUI resources after test case completes
Hi Rao, As I mentioned in my first post, SoapUI doesnot completely shutdown when the test case has completed. At the very least, the connection pool threads are still running. Do you see those threads still running when the test case has completed? Do you know how to shutdown those connection pool threads (and whatever other bits of SoapUI are still running)? Thanks, -Dan7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.2KViews0likes2CommentsRe: Shutdown Test Case Runner and all ReadyAPI / SoapUI resources after test case completes
Hi Rao, I want SoapUI to shutdown after I have finished using it. When the test case ends, SoapUI is still running (or has left parts of its connection pool running). I don't really care about how it is done - SoapUI.shutdown() seemed like a reasonable candidate. What is the correct way to shutdown SoapUI and all the threads it has spawned after the test case ends? Thanks, -Dan7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.2KViews0likes4CommentsRe: Shutdown Test Case Runner and all ReadyAPI / SoapUI resources after test case completes
Hi - using the Java API. try { final SoapUIProTestCaseRunner proTestCaseRunner = new SoapUIProTestCaseRunner(); proTestCaseRunner.setEnableUI(false); ... proTestCaseRunner.run(); } finally { SoapUI.shutdown(); }7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes6CommentsShutdown Test Case Runner and all ReadyAPI / SoapUI resources after test case completes
Hi, After running a test case using theSoapUIProTestCaseRunner (setEnableUI(false)) it seems that some SoapUI threads are still running. This is after the test has completed and returned a result: 2017-06-07 11:43:56,843 [Thread-15] DEBUG com.eviware.soapui.impl.wsdl.support.http.SoapUIMultiThreadedHttpConnectionManager - Closing expired connections 2017-06-07 11:43:56,843 [Thread-15] DEBUG com.eviware.soapui.impl.wsdl.support.http.SoapUIMultiThreadedHttpConnectionManager - Closing connections idle longer than 30 SECONDS I've tried callingSoapUI.shutdown(), but the threads still continue to run. What is the correct way to shutdown SoapUI completely after a test case has completed? Thanks, -Dan7 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.3KViews0likes8CommentsRe: SoapUI project with Pro features run programmatically from Java code
For future readers, using the WsdlProjectPro in this manner is not supported - it does not load the license file. Recommendation is to use the SoapUIProTestCaseRunnerclass instead.7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.3KViews1like1CommentSoapUI project with Pro features run programmatically from Java code
Hi, I am trying to execute a specific test case within a Ready API / SoapUI NG Project. The test case contains Pro-only test steps. When the step is executed via the API, it returns an UNKNOWN result, and I see that the type of the step iscom.eviware.soapui.impl.wsdl.teststeps.registry.ProPlaceholderStepFactory$WsdlProPlaceholderTestStep I am starting the test suite with: final WsdlProjectPro project = new WsdlProjectPro("project.xml"); final TestSuite testSuite = project.getTestSuiteByName(this.suiteName); final TestCase testCase = testSuite.getTestCaseByName(this.caseName); testCase.getTestStepList().forEach(step -> System.out.println(step + " -> " + step.getName())); final TestRunner runner = testCase.run(new PropertiesMap(), false); I have a SoapUI licence that I have transferred to ReadyAPI. The soapui.dat and soapui.key files are present in USER_HOME/.soapui I assume that the placeholder step is created because the regular SoapUICore is being created without the extra factories registered by SoapUIProCore... What do I need to do to enable to pro features when running through the API? Thanks, -Dan7 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.4KViews0likes3Comments