When I worked on web services for the first time in Siebel the most difficult thing I found was to test them. When it comes to integration then the biggest challenge is to test it thoroughly and irony of integrations is that one or the other team always faces issues that test our patience and skills to the limit.
A lot of time we face a situation where the development is complete from out end but the other team is not ready. So, we can do one of the two things.
- Waste time waiting for other team to complete integration
- Test it from our end so that we can iron out the issue that we might face later.
But the question is how can I invoke webservice without the other application being ready?
The answer to this question is post below.
I was browsing through a forum when I came across a product called soapUI. soapUI is a tool to test web services and I decided to look at it’s features and found out that it is a pretty capable tool.
The biggest + for this tools is that it is open source which means that you don’t have to spend big dollars to use it.
It has got features like
- Inspecting Web Services
- Invoking Web Services
- Developing Web Services
- Web Services Simulation and Mocking
- Functional, Load and Compliance testing of Web Services
It is mainly aimed at developers and testers providing or consuming Web Services (Java, .net, etc). Functional and Load Testing can be done both interactively in soapUI or within an automated build or integration process using the soapUI command line tools.
Mock Web Services can easily be created for any WSDL and hosted from within soapUI or using the command-line MockService runner. IDE-plugins are available for
- Eclipse plug in
- IntelliJ IDEA plug in
- NetBeans plug in
soapUI requires Java 1.5 and is licensed under the LGPL license.
Visit the website soapUI yourself. It think it’s worth a try if you are into Siebel EAI.