Sunday, September 28, 2008

Finding Interoperability issues

During last few weeks I was involved in doing interoperability testing of WSF/C stack with .NET WCF. Actually what I understood was most of the times interoperability testing fails due to small errors like namespace mismatching, wrong payload, and ect. Actually the problem is most of the WS frameworks including .NET does not clearly indicate the error in some occasions. This makes the interoperability tester's work really hard.

Following are tips we can follow when some thing went wrong during interoperability testing.

1.Check the errors and log messages from the WS- frameworks
- This helps some times but in some situations the exceptions are misleading
2.Always send the messages through a message capturing tool
3.Always check the payload of the SOAP message is according to the schema.
4.Check the namespaces of the message elements.
5.Check specially the WS-Addressing elements in the message
6.Compare same framework's client-server messages with interoperability testing messages.
7.If your client is not working try to interop with your own service.
8.If the error cannot be found then ask from those framework authors.

No comments: