SoapUI is best in the league
Overall Satisfaction with SoapUI
We use SoapUI to verify all our APIs across multiple products. All the products have multiple interfaces: SOAP, REST, AMF, and JDBC. Primary focus is functional testing.
Pros
- Groovy scripting throughout! SoapUI can be extended to the limits of your imagination with Groovy. Add in the ability to import any .jar makes it very easy to create new functionality.
- WSDL refactoring is a very useful feature, especially in the early stages when the API is still being developed. This allows you to map existing tests to a new method that has been possibly renamed or even one who's parameters may have changed.
- Fully command-line driven allows tests to be scheduled with a task manager, or run through Maven from any continuous integration system.
- Recent release of API Dojo gives a lot of detailed information to the beginner as well as advanced users.
Cons
- JMS is the ugly step-child. Although the protocol is supported, the support is very limited. JMS is supported through a third-party add on (Hermes JMS), which is now very outdated (last update was 3 years ago).
- AMF is the other ugly step-child. AMF does not have any method discovery, so you need third-party tools (BlazeMonster) to help you craft your messages.
- REST, although this protocol was the main focus of the latest 5.0 release, still has some edge issues. Browse the SoapUI fora for details.
- Some parts of the documentation are outdated / incomplete.
- Lower the number of defects that get to production.
- Being able to craft specific messages, it is much easier to reproduce edge case problems.
- Tool can also be used for (very fast) data load runs into test environments.
- curl
curl is a pure scripting tool, SoapUI is a full IDE
Comments
Please log in to join the conversation