|
|
|
|
| Connectivity Verification |
| |
Connectivity verification is the process of verifying that Web services (and other systems connected with SOAP) exchange information correctly. In an internal enterprise system, this might involve verifying the connectivity between databases, Web servers, application servers, middleware, ERP systems, CRM systems, and legacy systems—all of which are internal modules. In a distributed Web service, this might involve connecting an internal module with partners' modules, or making an internal module available to any external client that wants to use it. In all cases, each module involved in this web of connectivity will act a SOAP server, a SOAP client, or both.
The key to verifying connectivity is to apply the divide and conquer methodology: isolate each module of the system and test it on its own, and then test the interactions between modules, adding them one at a time until you have tested all possible interactions. To verify whether a module operating as a SOAP server is functioning correctly, you would pull that module out of the system, then send requests to the server (via an emulated SOAP client) and verify the response. To verify whether a module operating as a SOAP client is functioning correctly, you would pull that module out of the system, then verify whether the client can correctly send requests to an emulated server, as well as whether the client behaves correctly when it receives a response from the emulated server. To test the interactions between multiple modules, you would create global test cases that impact multiple modules.
Read the Crosstalk Journal, July 200 article, "Security Issues with SOAP"
See also:
|
|
Read the following Parasoft technical white papers: |
| |
ZapThink report features Parasoft SOAtest
|
|
|
|
