Contributions
HTTP TEST REQUEST - wrong handling of upper case in url
Hi, I'm using Soapui Pro 5.1.2 official version (14 trial) I have used "HTTP TEST REQUEST" component as step I have observed two major issues during defining endpoint/url 1) There is no possibility to use upper cases. It not allow to use variables from Project/TestSuite/TestCase level. E.g. I have defined variable 2) If you are editing url in given place and type upper case letter it will automatically change focus to the end of field which make editing very confusing Regards, Piotr (pkitkows)10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes0CommentsRe: LoadTest - How to read/edit file/property in thread-safe way
I could use bellow code to serialize a list and get/remove first item from the list. myList = ["0", "1", "2", "3"] List<String> mySynchronizedList = Collections.synchronizedList(myList); order = mySynchronizedList.remove(0) log.info ("order: " + order) However, the mySynchronizedList has limited scope to only test step (groovy script). How I could do this globally ? (per suite, project) How can I return object from test step which will be accessible from another step? Regards1.6KViews0likes0CommentsRe: LoadTest - How to read/edit file/property in thread-safe way
Rao, Thank you for quick response. How delay will resolve this kind of issue ? Doesn't occurrence of this issue still be time("luck") randomized ? I have tried this: - Test Suite ( Property LIST - contains some entities) -- Test Case --- Test Step - groovy script which: ---- get LIST from SUITE ---- take first entity ---- remove first entity from LIST ---- save new LIST on the SUITE level --- Test step - some REST request based on data from groovy --- Test step - delay (randomized in range 0-50 ms) -> Added as you suggested --- Test step - groovy - do loop - jump to the first test step as long as LIST is not empty Unfortunately, this didn't help at all I tough that variables on case level are independent when you are using LoadTest, while a variables on the test suite/project level are shared between threads during LoadTEst execution. Does "PRO" version has some WA/solution ? Regards, Piotr1.6KViews0likes0CommentsLoadTest - How to read/edit file/property in thread-safe way
Hi, I'm trying to do some exercise with using SOAP UI and LoadTest function. My goal is to have test case/step which read data from property (as LIST) on the case/suite/project level (no matter), get first value and remove it from the list. It's working fine during single execution (SOAPUI). When I launch test case from LoadTest and use few threads, it happened sometimes that two or more threads read the same value. Is there any way to assure that reading and remove value from list (or file) will be done in thread-safe mode ? Any hints how to resolve that kind of issue ? Regards, Piotr2KViews0likes6CommentsJavaNullPointer during launching test step from grovy
Hi, I have following use case in soapui - TestCase -- TestStep - (groovy script) which contains project = testRunner.getTestCase().getTestSuite().getProject().getWorkspace().getProjectByName("PROJECT") testSuite = project.getTestSuiteByName("SUITE"); testCase = testSuite.getTestCaseByName("CASE"); runner = testCase.testSteps["MY_STEP"].run(testRunner, context); -- TestStep - (RunTestCase) with name "MY_STEP" When I executing such scenario from Soap ui everything seems to be ok. When I tried to launch it as Load Ui scenario I'm getting NullPointerException when executing runner from groovy script Mon Jul 07 22:28:07 CEST 2014:ERROR:java.lang.NullPointerException java.lang.NullPointerException at com.eviware.soapui.impl.wsdl.teststeps.WsdlRunTestCaseTestStep.run(WsdlRunTestCaseTestStep.java:251) at com.eviware.soapui.model.testsuite.TestStep$run.call(Unknown Source) at Script1.run(Script1.groovy:58) at com.eviware.soapui.support.scripting.groovy.SoapUIGroovyScriptEngine.run(SoapUIGroovyScriptEngine.java:96) at com.eviware.soapui.impl.wsdl.teststeps.WsdlGroovyScriptTestStep.run(WsdlGroovyScriptTestStep.java:149) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.runTestStep(AbstractTestCaseRunner.java:235) at com.eviware.soapui.impl.wsdl.testcase.WsdlTestCaseRunner.runCurrentTestStep(WsdlTestCaseRunner.java:48) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:148) at com.eviware.soapui.impl.wsdl.support.AbstractTestCaseRunner.internalRun(AbstractTestCaseRunner.java:43) at com.eviware.soapui.impl.wsdl.support.AbstractTestRunner.run(AbstractTestRunner.java:135) at com.eviware.soapui.impl.wsdl.loadtest.WsdlLoadTestRunner$InternalTestCaseRunner.run(WsdlLoadTestRunner.java:544) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Any help / hint would be appreciated. Regards839Views0likes1Comment- 2.1KViews0likes1Comment
- 10 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.5KViews0likes1Comment