This article is not about understanding the details of .NET WCF service, soapUI and Fiddler as all these three are quite popular things among .NET developers. And tools like soapUI and Fiddler may already be in the arsenal of many web developers and QA engineers.
Those who are new to these two tools should refer to following articles:
However, we will take a look into how Fiddler can be used to Monitor SOAP Request and SOAP Response transmitting behind the soapUI.
Let’s start with a simple WCF service in place. No need to have a WCF .NET Client as of now to test and monitor HTTP traffic of WCF service calls.
But why did we add Port No. 8888 in the proxy settings of soapUI? It is because Fiddler by default listens on port no. 8888.
If you have configured your Fiddler proxy tool to listen on some other port number, then you should use that one.
I hope you enjoyed this testing tip. No need to reiterate how blissful it is to test web services using soapUI and Fiddler if you are a web service developer/provider to remote clients.