What is most valuable?
We do a lot of web services testing and REST services testing. That is the focus of this product.
It has also enabled easy automation and concentration.
Working with the Parasoft team was very easy for us. They helped us get some of the solution customized, in terms of the things we needed, such as LDAP coding. We needed a special coding for that and we worked along with Parasoft to get that done successfully.
The primary use for us is the Web Services layer.
How has it helped my organization?
It enabled an easy integration of our adjacent platform that was for full automation. We did reach over 97% automation with the use of this tool. It was extremely lightweight.
The only unfortunate part is that as the organization no longer exists. Now there are different groups managing the tool.
Parasoft is not becoming the tool of choice for the next generation of software that we're building.
What needs improvement?
The feedback that we received from the DevOps of our organization was that the tool was a little heavy from the transformation perspective.
However, Parasoft seems to be working on a solution to make the tool slightly lighter. That is one of the things that could be improved.
Of course, it is a technical tool, so perhaps the interface could be better. We all have our struggles with any tools that we learn.
For how long have I used the solution?
We implemented Parasoft over five years ago.
What do I think about the stability of the solution?
In the beginning of the implementation, we did have some concerns in regards to the stability. Primarily, the concerns were about the licensing. We were not concerned that the application itself would crash. We never really experienced that and that did not become a problem for us.
What do I think about the scalability of the solution?
There were no issues with the scalability. It's a user-based licensed product. As long as you have enough licenses, you can just do whatever you need in order to scale it.
How are customer service and technical support?
In the beginning, we worked very closely with their technical support. They had great tech support and they did road shows once a year for us.
They would definitely listen to the concerns that we had and provided relevant feedback. The tech support is not just great, it is absolutely awesome!
Which solution did I use previously and why did I switch?
We were with HPE and they failed with their new product. It was not compatible with what we already had scripted.
The decision to switch was made in order to create more flexibility within the groups who were using the tools.
What's my experience with pricing, setup cost, and licensing?
The product is great. Sometimes companies make decisions based on the profit and not based on efficiency. The cost of Parasoft seems to have gotten higher with a projection that wasn't really stipulated for our company. They've done a tremendous job at negotiating those deals. We'll see what happens next.
Which other solutions did I evaluate?
We did look into a couple of open source tools. We also have an array of other suites that we could use. For example, we looked at the SoapUI NG Pro suite and a couple of other tools out there.
We felt that Parasoft would be a mutual gain with our team, and with our performance team, because they would use a lot of the performance-center items.
That was primarily why the company agreed on making a switch, so that it would benefit both areas in which we had concerns with the HPE products.
What other advice do I have?
My advice to anyone implementing this solution:
- Work closely with the tech support so that you don't get stuck on the little things.
- Since Parasoft provides tremendous tech support, work closely with them in order to get the first implementation and proof of concept done.
- You can then export from there based on your needs.