Contributions
Re: [Res]Automatically inserts additional tags in SOAP test step
Thank you Marcus. That worked. But can you explain or point me to the documentation that talks about SOAPUIPro preferences. I want to understand what it means changing "Default Request Editor" to Source, Outline, Form options. Thanks11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0CommentsRe: [Res]Automatically inserts additional tags in SOAP test step
Marcus, What kind of refactoring should I do? As some of my requests should have the listingSource container and some don't. I didn't really understand what change you are recommending. This service is not modified in recent times. I just started writing tests and ran into this issue. Thanks11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0CommentsRe: [Res]Automatically inserts additional tags in SOAP test step
I didn't do any changes to the WSDL. I should not change the existing WSDL. The example XSD that I provided is already existing in the WSDL. So there is no point of refactoring. I just modified the request in the SOAP test step by removing the "listingSource" container(please check the XSD that I quoted in the initial request). For some requests I need this container and some I don't need it.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.6KViews0likes0Comments[Res]Automatically inserts additional tags in SOAP test step
Hi SOAPUI-PRO team, I have created a sample SOAP request test step for one of the operation and modified the request according to my use-case. Which means, I removed some tags from the request. Noticed that tool automatically inserts these tags when ever I close the test step and open it. I am giving a sample XSD for which I notice this problem. <xs:complexType name="DraftCheck"> <xs:sequence> <xs:element maxOccurs="1" minOccurs="1" name="listingMode" type="xs:token"/> <xs:element maxOccurs="1" minOccurs="1" name="listingSource" type="tns:ListingSource"/> <xs:any maxOccurs="unbounded" minOccurs="0" processContents="lax"/> </xs:sequence> </xs:complexType> In my request, I just need only listingMode and not listingSource, so I deleted listingSource, but I keep getting back this tag contents(close the request and open it, you will see it). As this keeps appearing my tests fail. I looked at all the options in tool preferences, update definitions for WSDL, but didn't find any option to fix it. Any suggestions.. Thanks Surya11 years agoPlace ReadyAPI QuestionsReadyAPI Questions2.8KViews0likes7CommentsRe: [Resolved] Status returned as UNKNOWN
Thanks for the suggestions. It works after I added an assertion to validate valid HTTP response codes. Interesting I didn't realize till now that UNKNOWN is returned when we don't provide any assertions. But at-least by looking at the HTTP response code, the SOAPUI can provide status as OK(if code is 200) or UNKNOWN(code other than 200). Can this be treated as enhancement?11 years agoPlace ReadyAPI QuestionsReadyAPI Questions6.1KViews0likes0CommentsEnvironment switch doesn't work
Hi, I did respond to this issue in my original post and noticed that I did not get any response(guessing may be because the Subject for that forum request is set as [Resolved]). So created this new post. But please refer to my issue in this forum. viewtopic.php?f=2&t=21716 The suggestion I got is to rely on "environment" option in settings. I did try providing <environment> option and it didn't work. The value that I provided does not override with what is saved with the project. In maven pom.xml file, I defined the environment in configuration section as follows- <plugin> <groupId>eviware</groupId> <artifactId>maven-soapui-pro-plugin</artifactId> <version>4.5.1</version> <executions> <execution> <phase>test</phase> <goals> <goal>test</goal> </goals> <configuration> <projectFile>Trading-soapui-project.xml</projectFile> <junitReport>true</junitReport> <exportAll>true</exportAll> <outputFolder>${outputdir}</outputFolder> <settingsFile>../Common/soapui-settings.xml</settingsFile> <environment>QA</environment> </configuration> </execution> </executions> In the test case there is a Groovy test step that just prints the environment. Below is the simple Groovy script:- def env = testRunner.testCase.testSuite.project.getActiveEnvironment().getName() log.info "environment= ${env}" This always prints the environment value with what is saved in the project. The value that we provided does not override. I saved the project with environment as "Production", so the value displays as "Production" rather than "QA". Can you please validate if this functionality is working. Thanks in advance.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.1KViews0likes1CommentRe: [Resolved] Status returned as UNKNOWN
This is simple to create, just create a "Http test step" and provide the end point URL as "http://www.google.com". Response is returned and also you will notice in the Raw tab of the response the status is displayed as "Http/1.1 200 OK". But the result of this test step in SOAPUI is shown as "UNKNOWN".11 years agoPlace ReadyAPI QuestionsReadyAPI Questions6.1KViews0likes0Comments[Resolved] Status returned as UNKNOWN
Hi, I created a simple Http Test step and did provide a Http Get Request. Also noticed the GET call is made and the response status is returned as 200 (OK). But the report that is generated by SOAPUI shows the status as UNKNOWN. Why should the status return as UNKNOWN when it's OK(as response returned HTTP success code 200). Please refer to the attached file. I am concerned about this because I wrote a Custom report and I did code if the status of a test step is anything other than "OK" then it should report failure. Now the above example that I quoted should provide status as "OK" rather it shows "UNKNOWN" due to with the test case is listed as FAILED. Any suggestions will be helpful. Thanks11 years agoPlace ReadyAPI QuestionsReadyAPI Questions6.8KViews0likes7CommentsRe: [Resolved] Switch to different environments via maven
I did try providing <environment> option and it didn't work. The value that I provided does not override with what is saved with the project. In maven pom.xml file, I defined the environment in configuration section as follows- <plugin> <groupId>eviware</groupId> <artifactId>maven-soapui-pro-plugin</artifactId> <version>4.5.1</version> <executions> <execution> <phase>test</phase> <goals> <goal>test</goal> </goals> <configuration> <projectFile>Trading-soapui-project.xml</projectFile> <junitReport>true</junitReport> <exportAll>true</exportAll> <outputFolder>${outputdir}</outputFolder> <settingsFile>../Common/soapui-settings.xml</settingsFile> <environment>QA</environment> </configuration> </execution> </executions> In the test case there is a Groovy test step that just prints the environment. Below is the simple Groovy script:- def env = testRunner.testCase.testSuite.project.getActiveEnvironment().getName() log.info "environment= ${env}" This always prints the environment value with what is saved in the project. The value that we provided does not override. I saved the project with environment as "Production", so the value displays as "Production" rather than "QA". Can you please validate if this functionality is working. Thanks in advance.11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes0Comments- 11 years agoPlace ReadyAPI QuestionsReadyAPI Questions1.2KViews0likes0Comments