The "Web Services" and WCF technology are widely used for providing integration solutions between legacy software systems, as well as a part of a new-generation distributed systems built according to guidelines and principles of the Service Oriented Architecture (SOA). The loosely coupled nature of the modern distributed technologies encourages a new form of business - many companies start concentrating their efforts on developing web services that can be used by other industry players for creating final applications.
SOA Cleaner reads the web service definition document (WSDL) and generates a graphical user interface required for composing a message to be sent to the web service in a native and very intuitive way. Several aspects of the request such as input arguments, http headers, attachments etc. are available for editing through a generated graphical user interface. A full business process can be easily emulated, by defining sequential web service calls. The response returned from the web service can be verified by defining assertions, or used as an input for following calls.
SOA Cleaner aims to cover many standards defined by the WWW Consortium for the Service Oriented Architecture (also known as WS-* standards). SOA Cleaner supports REST testing as well (including WCF WebHttpBinding).
The main benefits of SOA Cleaner differentiating it from similar solutions are:
a. Intuitive and usable - no coding knowledge is needed. Notions of scripts, projects, flow control and parameterization are all handled in a simplified, friendly and intuitive way.
b. Microsoft based - all written in Microsoft .NET, SOA Cleaner exploits the power of .NET for WS-* standards and thus it is compliant with Microsoft WCF, without losing a high level of interoperability with Java-based Web Services frameworks.
c. High performance - SOA Cleaner is light weighted, no cumbersome infrastructures are used.
d. Suitable for performing both QA and dev-tests.
e. REST support.
Web Service, WCF (including WebHttpBinding) and REST invocation.
Select WCF deferent binding and security.
Tree grid for editing requests.
Define assertions for response checking.
Edit Http headers.
Define WCF client credentials (Basic, Windows, Http Digest, certificate and Mesh).
Adding random number or string, or information from a CSV file, to a request.
Creating a loop, where each invocation uses a different input from a CSV file.
Full business process emulation; defining several steps and running a full test.
Adding information to a request, from previous responses.
Save and open tests.
Edit proxy settings.
Command line test execution.
A conditional invocation can be added, where execution depends on a previous response.