ContributionsMost RecentMost LikesSolutionsRe: test suite startup script not executed from command lineOK, so by removing the test case (c) switch the test suite setup script is now executed. So, test suite setup scripts will not be executed if test case (c) switch is set, then. Is there no mention of this limitation in SoapUI documentation? Is this a known issue? Could this be fixed?Re: test suite startup script not executed from command lineThanks for your replies, Marcus. Regrettably, the test suite setup script is not executing. The script does run if I execute test suite from the UI. Here is last testrunner log: $ /soapui-pro-4.0/bin//testrunner.sh -s ts_ingestTestCases -S -cROGS-1003-VALIDATION -r -f 1387317890 -j -Ptitle=ROGS-1003-803348 file:/C://blah/path/blah/path/blah/path/blah.xml /soapui-pro-4.0/bin ================================ = = SOAPUI_HOME = C:\cygwin\SOAPUI~1.0 = ================================ soapUI Pro 4.0.2-SNAPSHOT TestCase Runner 17:09:43,734 WARN [SoapUI] Missing folder [C:\soapui-pro-4.0\bin\ext] for external libraries 17:09:44,669 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Users\ederber\soapui-settings.xml] 17:09:45,259 INFO [SoapUIProGroovyScriptEngineFactory] Setting Script Library to [C:\PROGRA~1\SMARTB~1\SOAPUI~1.1\bin\scripts] 17:09:46,501 INFO [SoapUI] File 17:09:46,620 INFO [WsdlProject] Loaded project from [file:/C:/cygwin//testing/rogers/labdrop3/automation/soapui_projects/Rogers_LD3.xml] 17:09:47,238 INFO [SoapUIProGroovyScriptEngineFactory] Setting Script Library to [C:\PROGRA~1\SMARTB~1\SOAPUI~1.1\bin\scripts] 17:09:48,183 INFO [SoapUIProTestCaseRunner] Setting project property [title] to [ROGS-1003-803348] 17:09:48,198 INFO [SoapUIProTestCaseRunner] Running soapUI tests in project [Rogers_cms] 17:09:48,198 INFO [SoapUIProTestCaseRunner] Running TestCase [ROGS-1003-VALIDATION] 17:09:49,033 INFO [log] i can has test case setup? 17:09:49,034 INFO [SoapUIProTestCaseRunner] Running soapUI testcase [ROGS-1003-VALIDATION] 17:09:49,121 INFO [SoapUIProTestCaseRunner] running step [ROGS-1003-VALIDATION] 17:09:53,264 INFO [SoapUIProTestCaseRunner] Finished running soapUI testcase [ROGS-1003-VALIDATION], time taken: 4120ms, status: FINISHED 17:09:53,274 INFO [SoapUIProTestCaseRunner] TestCase [ROGS-1003-VALIDATION] finished with status [FINISHED] in 4120ms SoapUI 4.0.2-SNAPSHOT TestCaseRunner Summary ----------------------------- Time Taken: 5076ms Total TestSuites: 0 Total TestCases: 1 (0 failed) Total TestSteps: 1 Total Request Assertions: 0 Total Failed Assertions: 0 Total Exported Results: 0 Re: test suite startup script not executed from command lineI have both lower case (s) and upper case (S) in the command. The upper case is there to save the project file after execution. Lower case does set the test suite: -sts_ingestTestCasestest suite startup script not executed from command lineFor debugging, I added log statements to the test case and test suite start up scripts: log.info "i can has test suite setup?" And log.info "i can has test case setup?" Here is my test runner command: testrunner.sh -sts_ingestTestCases -S -cROGS-1003-VALIDATION -r -f 1387309643 -j -Ptitle=ROGS-1003-212773 file:/blah/blah/project/path/blah.xml Based on test runner log, test suite setup script is not executed: ================================= = = SOAPUI_HOME = C:\cygwin\SOAPUI~1.0 = ================================ soapUI Pro 4.0.2-SNAPSHOT TestCase Runner 14:47:28,274 WARN [SoapUI] Missing folder [C:\soapui-pro-4.0\bin\ext] for external libraries 14:47:28,867 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Users\ederber\soapui-settings.xml] 14:47:29,418 INFO [SoapUIProGroovyScriptEngineFactory] Setting Script Library to [C:\PROGRA~1\SMARTB~1\SOAPUI~1.1\bin\scripts] 14:47:30,693 INFO [WsdlProject] Loaded project from [file:/C://blah/blah/project/path/blah.xml] 14:47:31,302 INFO [SoapUIProGroovyScriptEngineFactory] Setting Script Library to [C:\PROGRA~1\SMARTB~1\SOAPUI~1.1\bin\scripts] 14:47:32,313 INFO [SoapUIProTestCaseRunner] Setting project property [title] to [ROGS-1003-212773] 14:47:32,335 INFO [SoapUIProTestCaseRunner] Running soapUI tests in project [blah] 14:47:32,335 INFO [SoapUIProTestCaseRunner] Running TestCase [ROGS-1003-VALIDATION] 14:47:33,235 INFO [log] i can has test case setup? 14:47:33,290 INFO [SoapUIProTestCaseRunner] Running soapUI testcase [ROGS-1003-VALIDATION] 14:47:33,292 INFO [SoapUIProTestCaseRunner] running step [ROGS-1003-VALIDATION] 14:47:56,025 INFO [SoapUIProTestCaseRunner] Finished running soapUI testcase [ROGS-1003-VALIDATION], time taken: 22697ms, status: FINISHED 14:47:56,026 INFO [SoapUIProTestCaseRunner] TestCase [ROGS-1003-VALIDATION] finished with status [FINISHED] in 22697ms Where is the issue? Is test runner not getting at the test suite at all?Re: [Resolved] use amf requests for amf polling?Thanks, looking forward to checking it out.Re: [Resolved] use amf requests for amf polling?That would be great. And if this change makes it into a build I'd be happy to help test.Re: [Resolved] use amf requests for amf polling?Not currently, but maybe in the future?[Resolved] use amf requests for amf polling?Trying to set up some soapui tests that will work with the trader desktop web app from the blazeds turnkey download. I have an AMF Request includes the following initialization script: package flex.samples.marketdata; import flex.messaging.messages.CommandMessage amfHeaders["DSId"] = 'XXX' amfHeaders["DSEndpoint"] = 'my-polling-amf' object = new CommandMessage(0) parameters["Object"] = object; object.destination = 'market-data-feed' When sending the request though, I get the following response: <flex.messaging.messages.ErrorMessage> <clientId class="string">EEA7A7C1-130D-472E-C5FB-50C0C2A95E90</clientId> <destination>market-data-feed</destination> <messageId>EEA78926-9A1B-2042-4D5E-031849C6F2B2</messageId> <timestamp>1349201471805</timestamp> <timeToLive>0</timeToLive> <correlationId>EEB6D144-110C-ABEE-8F82-A83A623BC55F</correlationId> <faultCode>Server.Processing</faultCode> <faultString>Destination 'market-data-feed' requires FlexClient support which was introduced in version 2.5. Please recompile the client application with an updated client framework.</faultString> </flex.messaging.messages.ErrorMessage> Is there some change I could make to get around this issue? Or would it require a change to soapui itself to get this to work?Re: xmlHolder for requests from other test casesUsing the following: def step = testRunner.testCase.testSuite.project.testSuites["TestSuite"].testCases["TestCase"].testSteps["testStep"] def groovyUtils = new com.eviware.soapui.support.GroovyUtils( context ) def holder = groovyUtils.getXmlHolder (step.testRequest.requestContent) It is possible to get node values, as follows: value = holder.getNodeValue(//v1:Request[1]/v1:Id[1]") But I have had no success with setting node values. I have tried: holder.setNodeValue("//v1:Request[1]/v1:Id[1]", "2") And holder["//v1:Request[1]/v1:Id[1]"] = "2" To no availxmlHolder for requests from other test casesIs there a way to use xmlholder to get at some xml from another test case, and set values in that request? i.e., test case A has a groovy script test case B has a collection of XML test requests. How can test case A's groovy script set values in the XML from test case B?