DouglasY
Occasional Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
SoapUI testrunner ERROR com.eviware.soapui.SoapUI - An error occurred [Unrecognized option: -F]
I am configuring my testrunner command line per the instructions in https://www.soapui.org/test-automation/running-from-command-line/functional-tests.html I'm getting an error. Is the page linked above correct for SoapUI 5.5.0 testrunner? Note: I have tried with and without a space between the option "-F" and the style "XML", i.e.: -F XML -FXML How can I fix this? /usr/platform/SoapUI-5.5.0/bin/testrunner.sh -I -j -f output -F XML -a -Gnode1=linuxhost1 -Gnode2=linuxhost2 -s 'Smoke Test Launch TestSuite' 5010-837-Smoke-Test-Project-soapui-project.xml ================================ = = SOAPUI_HOME = /usr/platform/SoapUI-5.5.0 = ================================ SoapUI 5.5.0 TestCase Runner 2020-04-17 13:03:13,770 [main] ERROR com.eviware.soapui.tools.SoapUITestCaseRunner - org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -F 2020-04-17 13:03:13,771 [main] ERROR com.eviware.soapui.SoapUI - An error occurred [Unrecognized option: -F], see error log for details 2020-04-17 13:03:13,771 [main] ERROR soapui.errorlog - org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -F org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -F at org.apache.commons.cli.Parser.processOption(Parser.java:363) at org.apache.commons.cli.Parser.parse(Parser.java:199) at org.apache.commons.cli.Parser.parse(Parser.java:85) at com.eviware.soapui.tools.AbstractSoapUIRunner.initFromCommandLine(AbstractSoapUIRunner.java:151) at com.eviware.soapui.tools.AbstractSoapUIRunner.validateCommandLineArgument(AbstractSoapUIRunner.java:120) at com.eviware.soapui.tools.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:111) at com.eviware.soapui.tools.SoapUITestCaseRunner.main(SoapUITestCaseRunner.java:122) org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -F at org.apache.commons.cli.Parser.processOption(Parser.java:363) at org.apache.commons.cli.Parser.parse(Parser.java:199) at org.apache.commons.cli.Parser.parse(Parser.java:85) at com.eviware.soapui.tools.AbstractSoapUIRunner.initFromCommandLine(AbstractSoapUIRunner.java:151) at com.eviware.soapui.tools.AbstractSoapUIRunner.validateCommandLineArgument(AbstractSoapUIRunner.java:120) at com.eviware.soapui.tools.AbstractSoapUIRunner.runFromCommandLine(AbstractSoapUIRunner.java:111) at com.eviware.soapui.tools.SoapUITestCaseRunner.main(SoapUITestCaseRunner.java:122)Re: "Resource Root" property ${projectDir} and relative path
I know this is old, but I see no answers. Since I cannot find my answer, I'll probably have to formulate a new question, but I wanted to point out to the last commenter, nmrao, that ${projectDir} is mentioned in the ReadyAPI documentation... here's a link to one page I found today: https://support.smartbear.com/readyapi/docs/configure/workspaces/properties.html excerpt: To use the file path relative to the project directory, use ${projectDir}\data. For example: D:\projects\webservice\data\testdata.xls To use the file path relative to the directory that contains the workspace file, use ${workspaceDir}\data. For example: D:\projects\data\testdata.xlsIn a SoapUI NG response viewer, XML format, what does Alt-V Validate?
In SoapUI NG Pro, when looking at a response in the XML viewer, the right-click context menu shows a "Validate" option, with a keyboard alternative of Alt-V. What does this do? After some time searching and browsing the online documentation, I found some documentation of the XML Response panel, but there is no description of the right-click context menu popup or the functions these expose. I'm especially interested in where SoapUI is getting the information to report that it expected before the end of the content an element which is not present. The validation message is of the form: line 5: Expected element 'sampleElement@http://sample.name.space.com/SampleServiceResponseType' before the end of the contentRe: How do I test for non-existence of an XML element while avoiding error: Unexpected element: CDATA
I'm sorry that my plea for assistance is so unhelpful. This kind of reaction is why I seldom post to community forums. I already feel like an idiot because I can't figure it out on my own. If a community hero cannot understand me, maybe I should keep away. I want a groovy solution. Rather than the response, I think you want to see my request XML. The scripts I have are checking the request for existence of an XML element, which in my example I named nonExistentElement, then doing different validations on the response based on what answer comes back about how the request was formulated. The construct as I present in my sample code appears many times in many different scripts, and they are all generating errors which I would like to clean up. Whether I use the context expansion with an exact XPath, or one with wildcards as I have given, when the element is not there, I get a null back, which is all fine and good for the working of the script conditional branching; however, I also get an annoying error in the error logs and the Ready API logs about "Unexpected element: CDATA". I want to eliminate the error by some means. I would like some way to evaluate in the groovy script whether an Xpath exists or not, but without generating an error in the case where the Xpath does not exist.How do I test for non-existence of an XML element while avoiding error: Unexpected element: CDATA
// The following sample is based on advice given on SmartBear community about how to check for the non-existence of an xml element // https://community.smartbear.com/t5/SoapUI-Open-Source/How-to-check-non-existence-of-a-xml-element/m-p/37511/highlight/true#M15180 def testStepName = context.testCase.getTestStepAt(context.getCurrentStepIndex()).getLabel() def expectNull = context.expand( '${'+testStepName+'#Request//*:nonExistentField}' ) assert expectNull.isEmpty() // The assertion works as expected; however, the code generates an error when expanding the Xpath // ERROR:An error occurred [error: Unexpected element: CDATA], see error log for details // How do I test for non-existence of an XML node without generating an ERROR in SoapUI?
