Contributions
Re: Re: TestCaseRunner not selecting a particular testcase
Hi Nenad, Thanks for the suggestion. We did try to run without the space after "-c", but the result was the same. You'll have noticed that the space didn't prevent "-s" from working correctly in the original command, in that the TestSuite got narrowed down. /Steve1.3KViews0likes0CommentsRe: TestCaseRunner not selecting a particular testcase
Hi, We've tried to run SOAPUI on the (Windows) command line and select a particular TestSuite & TestCase to run. According to the output logs, TestCaseRunner correctly narrowed down the TestSuite, but did not narrow down the TestCase (it ran both TestCases that existed in the TestSuite, not just one). I have copied the command that we ran (using the -s and -c arguments as suggested) and the stdout as a result. I have also attached the project file that the command executes. Thanks, Steve Professional license, Insurance Australia Group D:\eventures>"C:\Program Files\Java\jdk1.6.0_10\bin\java" -Xms128m -Xmx1024m -Dsoapui.home="C:\Program Files\eviware\soa pUI-Pro-3.0-beta-2\bin" -cp "C:\Program Files\eviware\soapUI-Pro-3.0-beta-2\bin\ext\*;C:\Program Files\eviware\soapUI-Pro-3.0-beta-2\bin\soapui-pro-3.0-beta-2.jar;C:\Program Files\eviware\soapUI-Pro-3.0-beta-2\lib\*;D:\dev\app\apache-ant-1.7.1\lib\*;" com.eviware.soapui.SoapUIProTestCaseRunner -e http://dev-eventures-esb:17000/ -s "eV-DP-CalculateMotorPremium-0-003_POS01_MinimumData" -c "eV-DP-CalculateMotorPremium-0-003_POS01_MinimumData_DataDriven" "D:\eventures\workspace\src\Eventures\POT\trunk\DataPower\test\local\services\calculatemotorpremium\eV-DP-CalculateMotorPremium-0.003-soapui-project.xml" soapUI Pro 3.0-beta2 TestCase Runner 14:00:49,835 INFO [SoapUI] Added [file:/C:/Program%20Files/eviware/soapUI-Pro-3.0-beta-2/bin/ext/ant.jar] to classpath 14:00:49,835 INFO [SoapUI] Added [file:/C:/Program%20Files/eviware/soapUI-Pro-3.0-beta-2/bin/ext/jt400.jar] to classpath 14:00:49,835 INFO [SoapUI] Added [file:/C:/Program%20Files/eviware/soapUI-Pro-3.0-beta-2/bin/ext/postgresql-8.3-604.jdbc3.jar] to classpath 14:00:49,835 INFO [SoapUI] Added [file:/C:/Program%20Files/eviware/soapUI-Pro-3.0-beta-2/bin/ext/postgresql-8.3-604.jdbc4.jar] to classpath 14:00:49,835 INFO [SoapUI] Added [file:/C:/Program%20Files/eviware/soapUI-Pro-3.0-beta-2/bin/ext/serializer.jar] to classpath 14:00:49,835 INFO [SoapUI] Added [file:/C:/Program%20Files/eviware/soapUI-Pro-3.0-beta-2/bin/ext/sqljdbc.jar] to classpath 14:00:49,835 INFO [SoapUI] Added [file:/C:/Program%20Files/eviware/soapUI-Pro-3.0-beta-2/bin/ext/xmlunit-1.2.jar] to classpath 14:00:50,055 INFO [DefaultSoapUICore] initialized soapui-settings from [C:\Documents and Settings\sys_eventures_build\soapui-settings.xml] 14:00:50,385 INFO [SoapUIProGroovyScriptEngineFactory] Setting Script Library to [D:\eventures\workspace\src\Eventures\POT\trunk\DataPower\test\script-library] 14:00:50,385 INFO [DefaultSoapUICore] Adding listeners from [C:\Program Files\eviware\soapUI-Pro-3.0-beta-2\bin\listeners\demo-listeners.xml] 14:00:50,836 INFO [WsdlProject] Loaded project from [file:D:/eventures/workspace/src/Eventures/POT/trunk/DataPower/test/local/services/calculatemotorpremium/eV-DP-CalculateMotorPremium-0.003-soapui-project.xml] 14:00:51,988 INFO [SoapUIProTestCaseRunner] Running soapUI tests in project [eV-DP-CalculateMotorPremium-0.003] 14:00:51,988 INFO [SoapUIProTestCaseRunner] Running TestSuite [eV-DP-CalculateMotorPremium-0-003_POS01_MinimumData], runType = SEQUENTIAL 14:00:51,988 INFO [SoapUIProTestCaseRunner] Running soapUI testcase [eV-DP-CalculateMotorPremium-0-003_POS01_MinimumData_DataDriven] 14:00:51,998 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Load Template Script] 14:00:52,048 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Load Additional Assertions] 14:00:52,088 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Load Parsing Script] 14:00:52,108 INFO [SoapUIProTestCaseRunner] running step [DataSource] 14:00:52,388 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Set Request Template] 14:00:52,428 INFO [SoapUIProTestCaseRunner] running step [Property Transfer] 14:00:52,749 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Parse Request] 14:00:52,979 INFO [SoapUIProTestCaseRunner] running step [CalculateMotorPremium - Test] 14:00:57,265 INFO [SoapUIProTestCaseRunner] Assertion [SOAP Response] has status VALID 14:00:57,265 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Verify Additional Assertions] 14:00:57,486 INFO [SoapUIProTestCaseRunner] running step [DataSource Loop] 14:00:57,496 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Set Request Template] 14:00:57,496 INFO [SoapUIProTestCaseRunner] running step [Property Transfer] 14:00:57,556 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Parse Request] 14:00:57,686 INFO [SoapUIProTestCaseRunner] running step [CalculateMotorPremium - Test] 14:01:01,421 INFO [SoapUIProTestCaseRunner] Assertion [SOAP Response] has status VALID 14:01:01,421 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Verify Additional Assertions] 14:01:01,421 INFO [SoapUIProTestCaseRunner] running step [DataSource Loop] 14:01:01,622 INFO [SoapUIProTestCaseRunner] Finished running soapUI testcase [eV-DP-CalculateMotorPremium-0-003_POS01_MinimumData_DataDriven], time taken: 9419ms, status: FINISHED 14:01:01,622 INFO [SoapUIProTestCaseRunner] Running soapUI testcase [dfgklsd] 14:01:01,622 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Load Template Script] 14:01:01,642 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Load Additional Assertions] 14:01:01,662 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Load Parsing Script] 14:01:01,682 INFO [SoapUIProTestCaseRunner] running step [DataSource] 14:01:01,892 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Set Request Template] 14:01:01,912 INFO [SoapUIProTestCaseRunner] running step [Property Transfer] 14:01:01,972 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Parse Request] 14:01:02,132 INFO [SoapUIProTestCaseRunner] running step [CalculateMotorPremium - Test] 14:01:05,988 INFO [SoapUIProTestCaseRunner] Assertion [SOAP Response] has status VALID 14:01:05,988 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Verify Additional Assertions] 14:01:06,108 INFO [SoapUIProTestCaseRunner] running step [DataSource Loop] 14:01:06,118 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Set Request Template] 14:01:06,118 INFO [SoapUIProTestCaseRunner] running step [Property Transfer] 14:01:06,178 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Parse Request] 14:01:06,298 INFO [SoapUIProTestCaseRunner] running step [CalculateMotorPremium - Test] 14:01:09,954 INFO [SoapUIProTestCaseRunner] Assertion [SOAP Response] has status VALID 14:01:09,954 INFO [SoapUIProTestCaseRunner] running step [Groovy Script - Verify Additional Assertions] 14:01:09,954 INFO [SoapUIProTestCaseRunner] running step [DataSource Loop] 14:01:10,134 INFO [SoapUIProTestCaseRunner] Finished running soapUI testcase [dfgklsd], time taken: 8322ms, status: FINISHED 14:01:10,134 INFO [SoapUIProTestCaseRunner] TestSuite [eV-DP-CalculateMotorPremium-0-003_POS01_MinimumData] finished with status [FINISHED] in 18146ms2.6KViews0likes5CommentsRe: Assertions with partial wildcards?
Hi Ole, Sorry for not replying sooner... I don't check the forums very often, just when I run into problems with no obvious solution, such as http://www.eviware.com/component/option ... 28.0 - I can send my project file for that if you like Anyway, yes I think your idea about adding regex's to the XPath assertion is excellent. Whatever syntax you choose is fine with me, so long as it's sufficiently documented (the User Guides are well-written, but of course they weren't designed to cover every possible scenario - especially when the power of Groovy is factored in). I do agree with you in that the regex should not share the same syntax as property expansion; that would just be confusing. FYI, in the meantime I did resort to using script assertion steps to perform the wildcard matching of values in responses. It wasn't too painful, since Groovy has very good XML support. Thanks, Steven1.7KViews0likes0CommentsRe: specifying multiple endpoints using the command line tool testrunner.bat
Hi Ole, I read the sourceforge post and have a follow-up question: If you go with the suggested approach of specifying endpoints via global properties, does that mean you need to abandon the -e option in the command line arguments? I have a test case which tests a number of interfaces, and all but one of them needs to be directed to the same endpoint (ie, only one interface needs to be re-directed elsewhere). I would have like to continue using -e, but have control over the endpoint *just* for that one particular interface. Thanks, Steve772Views0likes0CommentsAssertions with partial wildcards?
Hi, is it possible for the open-source version of SoapUI to do assertions that combine wildcards as well as static values? For example, if I have a SOAP response that looks like this; Quick brown fox Would I be able to create an assertion that verifies the presence of the word "brown", and not care about any other text around it? So I'm thinking my assertion would be an XPath along the lines of *brown* Better yet, if wildcards work on just the value (without the XML block enclosing it), I'd use a more specific XPath to verify the response, so the value of //tag/response must be [*brown*] Ideas anyone? Thanks, Steve PS - yes this is a trivial example, but I do have a real-life application that's returning messages that include both static and dynamic text components in an element, and I really want to verify the static components.3.1KViews0likes3Comments