Parasoft SOAtest Reviews

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.

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.

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.

We implemented Parasoft over five years ago.

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.

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.

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!

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.

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.

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.

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.

• Has the ability to add regression controls and scripts in different languages for parts of the test script.

• Regression controls help to create a baseline response and ignore the dynamic values, so we can compare against any future builds. We can tell the impact of any change right away. We can tell which APIs we need to focus on for the API backward compatibility. This feature was not found in any other product that I have used.
• The scripting support provided for Java scripts and languages that rely on Java is very helpful. This skill is easy to find in the industry.

It used to take a couple of days to run several scenarios of the billing project at AOL. I was able to automate a collection of 72 APIs and the back-end batch jobs, so as to run the whole thing in under 30 minutes.

I was having trouble with the browser automation on my Mac laptop. They need to make it easier, so as to configure and run this tool on Mac.

I have tried to automate purchasing QuickBooks from our corporate intranet. I could not signup for the Free Trial from the below URL, due to security certificate issues:

https://quickbooks.intuit.com/...

I got busy on other projects and did not revisit this. Apparently, I did not have similar kind of issues while using the Windows OS laptop, in the past.

There were no stability issues.

There were no scalability issues.

A few years ago, I would have given technical support a rating of 10/10. However, I would now give them a rating of 7/10.

Its ease of use and the variety of protocols that it supports are the main reasons why we switched solutions.

The setup was straightforward.

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

This is the best tool for API and back-end automation.

It improved my project ROI in various portions of the testing life cycle.

1. The Parasoft reporting feature needs to be more effective in terms of status graphical representation. Parasoft report doesn’t provide graphical representation, meaning summary of report which indicate - how many test scenarios passed or failed, basically the management is expecting this kind overall summary report. So far, the Parasoft report will be prepared manually and sharing with other stakeholders. 

2. I personally feel that 50% of Parasoft features are provided by SoapUI free of cost. However, not all the webservices protocols.SoapUI is an open source tool that supports most protocols such as SOAP, REST, HTTP, JMS, AMF, and JDBC. From a business perspective, why should a company invest money on Parasoft licensing which has a high cost

3. We cannot use the WebUI testing in full mode and we need more focused improvements in that area. I tried to use Parasoft for functional testing (web testing), such as clicking a button and selecting a value from a dropbox, but I figured out that the tool is mostly built for web service automation and User Interface automation. For instance, HPE UFT is a tool with a bundle of features(web service automation and functional automation). I know Parasoft supports basic WebUI automation but with limitations.

• Tool offers easy ability to rapidly set up functional test scenarios
• The tool interface is very user friendly and the user guide is a great help
• Tool allows custom scripting and integrates well with most frequently used Source Control tools
• Utilizing features that support Data Driven testing and E2E has increased efficiencies drastically

5 Years. I have used the tool mostly for Web Service Testing.

ParaSoft offers a great customer service, its a great combination along with a good product.

Excellent and very approachable!

• API support for JSON and REST payload
• Virtualization
• Complete visibility of all the conditions, circumstances, and influences surrounding and affecting the testing of software servers and environment

It provides easy handling of RESTful API's and figuring out exact API scalabilty, responses, and failed API's, returning code captured by the fault injections.

More descriptive reports are needed.

I've used it for six months.

No issues encountered.

No issues encountered.

No issues encountered, however, more scalability is needed, especially when testing in elastics/cloud platforms.

8/10.

9/10.

We previously used JMeter and were offered better support from Parasoft. As well as this, the reports and user friendliness of SOAtest helped us make the decision to switch.

It's very easy to set up and doesn't take much time. You don't need installation expertise to set it up.

We used a vendor team from Parasoft themselves who were very good.

It's 100%.

The price is a little expensive in terms of users.

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

Even validate SOASTA tool too.

The most valuable features are the Browser Playback tool for recording and playing web scenarios (Web UI testing), and the messaging client for sending SOAP calls and for validating responses.

The testing time is shortened because we generate test data automatically with SOAtest.

During the process of working with SOAtest and building test cases, the .TST files will grow. A negative side effect is that saving your changes takes more time. The bigger the .TST file, the more time it costs. Sometimes a few seconds! An option is to split up the file into separate files, but often that’s no realistic option because you want to keep the test suites together.

TST-file is the container file in which all testsuites and teststeps are stored. It often happens that you have to change a teststep and want that change to be saved. Saving your teststep in an almost empty container (with only one testsuite and a few teststeps) will go very fast (within 1 second). Saving your step in a container with multiple testsuites and teststeps takes a lot more time. In my case sometimes five seconds.

Sometimes SOAtest hangs, but that is very sporadic. It could be caused by the stability of the environment of the customer in general.

We haven’t had any scalability issues.

The technical support in the Netherlands is very good. Questions about the tool are almost answered within a day. When needed, a Parasoft consultant joins the project for one day or more.

We used SoapUI for testing web services. In our case, the advantage of using Parasoft SOAtest is the use of the datasheet; with one message, you can loop through your datasheet and check all your data.

The setup was done by another team of the company and was out of our scope.

The products of Parasoft have the name; they’re expensive. I think it would be a great step to decrease the price of the licenses. A possible consequence could be getting more users and more familiarity in the Netherlands and around the world.

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.

Invest a lot of research time into what your exact needs are. After that, select some test tools to compare all the options. In my opinion, Parasoft has so many possibilities that it must have a place on your shortlist!

XML assertions, XML data bank, various tools available internallly

Achieved testing middleware services and automating them with the features in SOATest. API testing is made easy. Automation and regression test suite was achieved without the need to write much code.

Performance of the tool

5 years

No

Performance issues if there are too many sessions open on your system.

Good

Good

No

Easy

Knowledgeable

Web services and API test automation was made simple without writing much code.

I have used SOATest 9.6 and 9.8 version in my project for automating the webmethods. It is widely recognized as the leading enterprise-grade solution for API testing and API integrity. Thoroughly test composite applications with robust support for REST and web services.

It provides easy handling of RESTful API's and figuring out exact API scalability, responses, and failed API's, returning code captured by the fault injections. We also used other utilities provided by Parasoft like, Datasource, Extension tools and DB tools which reduces most of our manual effort and increased the requirement coverage in automation.

The beauty of Parasoft SOA test tool is that it will support more scripting languages based on QA engineer comfort.

1. More descriptive reports are needed. Very high level reporting is not available.

2. Also the price is a little expensive in terms of users when compared to other similar tools available in the market.

3. WorkSpace is getting corrupted very often.

4. Integrating with other test management tools is really difficult.