We evaluated several home-grown and open-source tools such as JMeter, Postman, and SoapUI.

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.

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.

We evaluated SmartBear SoapUI.

I looked at SoapUI NG Pro.

I have experience with a lot of other products, but when I started with this job (Dutch Government) three years ago, the product, SOAtest, had already been bought by the company.

We evaluated JMeter as well, which was our existing product.

We mainly looked into the SoapUI solution, along with some Selenium software and besides that, other stand-alone database tooling options. We also evaluated manual testing.

I joined my current project at a later stage, but I’m sure that other options were evaluated before choosing Parasoft SOAtest for this project. Unfortunately, I don’t know which other options were evaluated.

We evaluated IBM RTW. I think it has a little bit more control, but it’s more expensive.

We did evaluate the other options in the market, Tosca and SoapUI, which we evaluated. Ultimately, we went with this tool.

Yes, but before I was involved, so I don’t know more than that.

We followed our customer’s choice.