Compare test step
Purpose The process of testing often requires to compare test results to expected values. When we need to check a specific value, we can use assertions. However, there are often occasions when we need to compare one documents to another (e.g. XML, JSON). I propose to introduce a new type of test step: Compare test step. Functionality Compare test step would allow: Select documents: users would select source and target document from test step requests, responses, properties and other document holders in SoapUI environment, similarly as the Property Transfer test step does. Type of comparisson: the user could choose whether the documents have to be identical (both structure and values) or similar (only the structure should be same). Also the user could choose to ignore differences in whitespaces, attributes, or namespaces, or even data types which to ignore (e.g. xsd:dateTime is typically different). List of items to compare/ignore: the user could list the items which should be ignored, represented by XPath statements. Also there would be an opposite option: a list of XPath statements to check and to ignore the rest of the documents. Suggestions The Compare test step can utilize the XMLUnit library for XML and thus expose its function via SoapUI user interface. The Compare step can be similarly used for JSON documents.9KViews8likes3CommentsSoapUI - Folders in Projects
Right now the only grouping possible is by project, it would be nice to be able to have folders inside this projects. This way the "workbench" can be a little cleaner. Anyway, thanks in advance and thanks for such a helping tool. Best regards and keep up the wood work! Federico.6.9KViews4likes2CommentsSoapUI Maven Plugin v5.2.2
Hello, Disclaimer: This is a cross-post fromhttp://community.smartbear.com/t5/SoapUI-Open-Source/soapui-maven-plugin-5-2-0-not-published-to-SmartBear-repository/td-p/102327 which does not seem to get any more attention from SmartBear. The issue: The latest version of SoapUI Maven Plugin published to maven (and also smartbear maven repo,http://smartbearsoftware.com/repository/maven2/com/smartbear/soapui/soapui-maven-plugin/) is 5.1.3. This version does not support the -reallyimportant- JsonPath assertion. From the SoapUI github repository it can be seen that version 5.2.2 is ready, and can be built. It is understood that SmartBear tries to promote and give more support to SoapUI pro edition and the readyApi suite, but please, do not fail your longtime users and show some respect and support to the community. There projects that due to their size cannot be migrated to readyApi at the moment while need the JsonPath assertions. Don't get my attitudewrong, but try to understand. It is really bad to discover broken functionallity when your CI server reports no errors, since it is using a maven plugin thatsimply ignores this type of assertion.Solved5KViews3likes5CommentsHow to use properties( either mock service or project) in resource path of mockService?
HI, Iwant to use custom properties of mock service or project as variable in mock service resource path. Any way to do it ? Test Case Endpoint:http://localhost:9100/v1/customers- it send authorization as header which contain token to be used by mock service. Mock service running on : 127.0.0.1:8181/api Mock Service End Point: /customer/101068577 /customer/101068577/loyalty/relationship I am able to transfer property from project level to mock service, but unable to use mock service property in resource path. Actual: Mock service unable to read value from mockService custom property. Expected: mock service resource url : /customer/${#mockService#Customer_ID_Default} /customer/${#mockService#Customer_ID_Default}/loyalty/relationship or /customer/${#Project#Customer_ID_Default} /customer/${#Project#Customer_ID_Default}/loyalty/relationship1.5KViews1like1CommentHow to enable custom log for SOAP UI for each run
Hi , I enabled Http Logging by adding the following to soapui-log4j.xml : <appender name="FILE-HTTP" class="org.apache.log4j.RollingFileAppender"> <errorHandler class="org.apache.log4j.helpers.OnlyOnceErrorHandler"/> <param name="File" value="${user.home}/.readyapi/logs/ready-http.log"/> <param name="Threshold" value="DEBUG"/> <param name="Append" value="true"/> <param name="MaxFileSize" value="5000KB"/> <param name="MaxBackupIndex" value="50"/> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="%d %-5p [%c{1}] %m%n"/> </layout> </appender> <logger name="org.apache.http.wire"> <level value="DEBUG"/> <appender-ref ref="FILE-HTTP"/> </logger> This works when I run the test and logs all http information to the log at the location. Issue : 1) This custom log now disables the http log in the SOAP UI Console 2) The log does not get created at the SOAP UI project folder , only at the given path. What is the config change required to get the custom log at the project root level when run from the test runner?2.6KViews1like0CommentsSoapUI - Remember path of last added wsdl
If you need to add two or more WSDLs from your file system, every fileyou add starts the "browse" dialog from SoapUI's instalation folder. It would help a lot if the last path is remebered, so no need to navigate to the directory every time. Thanks again. Best regards, Federico.1.6KViews1like0Comments