What is our primary use case?
The primary use case for adopting Parasoft SOAtest is to test web services/middleware testing (SOAP/REST/MQ/SAP RFC/EDI/FTP).
- REST: WADL and JSON.
- SOAP: WSDL.
- SAP RFC
- Message queuing supported: JMS, MQ, and NET WCF.
- Protocols supported: TCP/IP, FTP, EDI, WSDL, WADL, WS-*, UDDI, RMI, EJB, webMethods, TIBCO, SMTP, and custom.
- Third-party tool integration (plug and play)
- Stored procedure testing and DB validation
- UI recording through Selenium WebDriver.
- I've used this solution for more than 6.7 years.
How has it helped my organization?
Parasoft SOAtest has improved the quality of our automated web services, which can be easily implemented through service chaining and service virtualization.
The best feature to integrate with third party tools is the integrated plug and play without any rework, which makes it more valuable than any other tools.
Parasoft SOAtest has more visibility in regards to testing support data and reporting mechanisms.
Through Parasoft SOATest, we can automate our scenarios in a data driven format, which shows there is no rework on scripts. We only need to update the test data and run for a number of scenarios.
- Easy handling of RESTful APIs/SOAP calls.
- Getting the data on the API performance side, such as response time and segregation of failed API issues based on returning code captured by fault injections.
- Comparison of current responses with baseline response to figure out issues in case of failure with an exact location point.
What is most valuable?
- Diff control tool
- Different service types of support (SOAP, REST, SAP RFC, and UI recording)
- Third-party tool integration: GitHub and Jenkins.
- Plug and play
- Service virtualization
What needs improvement?
Reports could be customized and more descriptive according to the user's or company's requirements.
For how long have I used the solution?
More than five years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
How are customer service and technical support?
I have had an awesome experience while working with the customer service/technical support teams. They have resolved issues within a day or two.
If issues are reported to the Parasoft Support Team, they will resolve them by taking it to t-con or v-con. Also, they are very supportive and well-versed with the proper information.
Which solution did I use previously and why did I switch?
We have been using this solution for more than 6.7 years.
I have used other solutions as well, but I did not get proper support during our testing due to the constraints for testing in particular areas.
How was the initial setup?
It is simple to do the setup starting from installation until usage. It does not require any specific skill (i.e., it is the same as any other tool installation).
What about the implementation team?
They were well-versed with the proper information.
What was our ROI?
We are completed satisfied with Parasoft SOAtest. The ROI is more than 95%.
What's my experience with pricing, setup cost, and licensing?
It is a commercial tool. The license price is a little expensive, but it provides a better outcome in terms of the end-to-end automation process.
Which other solutions did I evaluate?
While evaluating tools for web service testing, I tried different solutions (freeware and highly-used), but they did not provide some mechanism/features that I could test my respective scenarios to FTP, EDI, MQ, and even SOAP calls. Because of this, I moved back to the existing solution.
What other advice do I have?
I have been using this solution for more than six years. I have not found any issues while doing automation.
Which version of this solution are you currently using?