Hi,Can anybody tells about the difference between SOAP Fault & Not SOAP Fault & SOAP Response?How it differs each other, Advantages in soapUI testing etc.^Regards

Hi,When you send a SOAP Response, you generally get a SOAP Response. Now this SOAP Response can either be a SOAP Fault or could be NOT SOAP FAULT. What SOAP FAULT means is that there is some issue(s) with the request XML you sent and it differs from the structure / format from the acceptable one as defined with schema. For example, if schema defines that following is an acceptable XML structure:<A>....<B>........<C>........</C>....</B></A>however you send the following XML structure in request, you will get a SOAP FAULT by the software that is doing that validation:<A>....<C>........<B>........</B>....</C></A>SOAP Fault is still a SOAP Response but it tells users that there is a "Fault" in the request that was sent.Let me know if you need more information.Thanks,Deepesh Jain

Thank you for the reply.Yes, I need more lights in to this. 1]Are you saying that SOAP Fault, Not SOAP Fault Assertions are validating the Requests and not on Response received?2] Whats a SOAP Fault? Whats is a NOT SOAP Fault? [I know these all are assertions in soapUI, I need beyond that]3] Can you brief with any example which differentiate each other?SOAP Fault, Not SOAP Fault - each success and failure scenarios.For Ref: Sample WSDL -http://www.oorsprong.org/websamples.cou ... e.wso?WSDLExampleRequest<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:web="http://www.oorsprong.org/websamples.countryinfo"> <soapenv:Header/> <soapenv:Body> <web:CapitalCity> <web:sCountryISOCode>USA</web:sCountryISOCode> </web:CapitalCity> </soapenv:Body></soapenv:Envelope>Response<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <web:CapitalCityResponse xmlns:web="http://www.oorsprong.org/websamples.countryinfo"> <web:CapitalCityResult>Washington</m:CapitalCityResult> </web:CapitalCityResponse> </soap:Body></soap:Envelope>^Regards

Well, in your original post you didn't talk anything about assertions. These assertions do validate only the responses not the requests. If you are looking to what these different assertions do, here is the updated response:1. SOAP RESPONSE : This assertion validates that the response received is actually a SOAP RESPONSE. Unless your webservice is down or something, you should always get this passed. If not, that means the response timed out and you didnt get a soap response. For example, how you sometimes get "Page cannot be displayed" when the web page is not available. Same concept2. SOAP FAULT : This assertion will validate that the SOAP Response that you got is actually a SOAP FAULT. For example, you might have sent an incorrect xml as a part of your test case and you are expecting that you would get a SOAP FAULT. In this case, you would have SOAP FAULT as your assertion. SOAP FAULT assertion will PASS your test case if you get SOAP FAULT in response.3. NOT SOAP FAULT : This is exactly opposite to the one above. If you do expect a valid SOAP RESPONSE, you would place this assertion, and this assertion will PASS your test case in case it gets a valid SOAP RESPONSE. If you placed this assertion, but in case you get a SOAP FAULT in your response, this assertion will fail the test case.With the example request and response you sent, the response if you notice is a good SOAP response and is not a SOAP FAULT. So for that particular response if you include both SOAP FAULT and NOT SOAP FAULT assertion, the former would FAIL while the latter will PASS.Hope this helps. Regards,Deepesh Jain

Hi Deepesh, Thank you for the reply. The level of information is good :-)However, I need more information towards difference of both...For Ex: if we put both SOAP FAULT & NOT SOAP FAULT assertions in a method and runs, we may get 4 cases... Case 1. [SOAP Fault Fail and Not SOAP Fault Success]Case 2. [SOAP Fault Success and Not SOAP Fault Fail]Case 3. [SOAP Fault Success and Not SOAP Fault Success]Case 3. [SOAP Fault Fail and Not SOAP Fault Fail]qn1. Can you please analyse above 4 cases and provide reasons?qn2. Whether SOAP Fault and Not SOAP Fault are reverse of one another?qn3. Do we need both these assertions really? since, SOAP Fault failure means Not SOAP Fault Success and vice versa.^Thanks

Wrong, you will only have case 1 and 2. SOAP FAULT and NOT SOAP FAULT are basically opposite of each other. If you put both the assertions one is bound to fail as both of them will validate the response for 1. SOAP FAULT2. NOT SOAP FAULTYou obviously cannot have both in the same SOAP step response.

ABCDEFG

Contributor

14 years ago

SOAP Fault Vs Not SOAP Fault

Hi,

Can anybody tells about the difference between SOAP Fault & Not SOAP Fault & SOAP Response?

How it differs each other, Advantages in soapUI testing etc.

^Regards

deepesh_jain
Frequent Contributor
14 years ago
If you would have placed NOT SOAP FAULT assertion in the same test case, yes it would have been valid.

Regards,
Deepesh Jain
pradeepbishnoi
Contributor
14 years ago
Hi,

The explanation given by Deepesh was very detailed, i guess it should have clarified your doubts.
However, to add couple of points from my end...

- There would be no real scenario where you can add both SOAP Fault & Not SOAP Fault assertion at same time. Since these 2 assertion are the compliment/opposite of each other. Hence status of that teststep would always be RED. [Standard says : RED status will take precendece over GREEN status]
- SOAP response would be RED only in case when you didn't received any response (it can be error or valid response) from server & the response tab is empty. It generally happens with the request time out (server not able to process the request in given time).
- SOAP Fault will always be RED, when you have a valid response ( which is not expected, expected result was an error )
- Not SOAP Fault will always be RED, when you have an error response (or fault tags in the response XML), here the expected response was a valid response.

Regards,
/Pradeep Bishnoi
http://learnsoapui.wordpress.com

Recent Discussions

Dan Technologies in Vikaspuri,Delhi
20 hours ago
DANTechnologies
Top 5 Reasons Why Saraf Furniture Stands Out in the Market
22 hours ago
saraf
Brand Hutt : Catch the Latest Looks
23 hours ago
brandhutt
com.eviware.soapui.config.* missing: How do I clone and run SoapUI locally in Intellij?
24 hours ago
mayur21
How Subhash Goel is Changing Pune
2 days ago
goelganga33565

Forum Discussion

SOAP Fault Vs Not SOAP Fault

Related Content

WCF WsHttp Binding SOAPUI returns BadContextToken fault

ReadyApi Maven Project fault running code WsdlProjectPro project = new WsdlProjectPro();

Soap Fault Issue

Fault occurred while processing.

Faulting module name: MSVCP140.dll

Recent Discussions

Dan Technologies in Vikaspuri,Delhi

Top 5 Reasons Why Saraf Furniture Stands Out in the Market

Brand Hutt : Catch the Latest Looks

com.eviware.soapui.config.* missing: How do I clone and run SoapUI locally in Intellij?

How Subhash Goel is Changing Pune