QA Lead at a financial services firm with 51-200 employees
Real User
Top 5
2025-04-04T15:11:00Z
Apr 4, 2025
One area that could use improvement is the cryptography capabilities in Parasoft SOAtest. It did not support enough of the protocols or cryptography formats we needed, which led us to create our own solutions.
Sr. Principal Software Engineer at Cadence Design Systems
Real User
Top 5
2023-10-10T08:37:40Z
Oct 10, 2023
Tuning the tool takes time because it gives quite a long list of warnings. Going through that is a challenge. It only happens in the initial stage when we are setting up the tool, but it can be improved. Parasoft SOAtest could add code coverage, which will help us do the coverage in a single tool.
UI testing should be more in-depth. Right now, they only have one feature: record and play. We need to have a bit more in terms of functionality. We hope they will improve on this in the future.
Sr. Principal Software Engineer at Cadence Design Systems
Real User
Top 5
2022-12-15T09:08:00Z
Dec 15, 2022
The summary reports could be improved because sometimes it is not very concise. The waiver process can also be improved because Parasoft SQAtest doesn't have a method to waive off one rule. Additionally, adding some guidance on providing standard templates could be helpful for new engineers or in complexity reduction. It could be sustained in a better way because it currently just gives the number that is a level of looping or callings. Hence, if something can be improved to refactor the code, then it should be code restructuring and all the information that can be provided to look at the complexity of the code.
Sr Quality Assurance Engineer at Wabtec Industrial
Real User
Top 10
2021-08-06T18:03:51Z
Aug 6, 2021
From an automation point of view, it should have better clarity and be more user friendly. Some aspects were difficult and therefore less useful for us, perhaps we lack the coding knowledge on that.
Test Automation Developer at a tech services company with 11-50 employees
Real User
2019-07-01T07:59:00Z
Jul 1, 2019
The product is very slow to start up, and that is a bit of a problem, actually. It is not as fast and it's a bit clunky, especially if you use it for the whole day or for a long time, it doesn't save the data, for example. So, it's a bit clunky and slow.
Parasoft SOAtest delivers fully integrated API and web service testing capabilities that automate end-to-end functional API testing. Streamline automated testing with advanced codeless test creation for applications with multiple interfaces (REST & SOAP APIs, microservices, databases, and more).SOAtest reduces the risk of security breaches and performance outages by transforming functional testing artifacts into security and load equivalents. Such reuse, along with continuous monitoring...
One area that could use improvement is the cryptography capabilities in Parasoft SOAtest. It did not support enough of the protocols or cryptography formats we needed, which led us to create our own solutions.
Tuning the tool takes time because it gives quite a long list of warnings. Going through that is a challenge. It only happens in the initial stage when we are setting up the tool, but it can be improved. Parasoft SOAtest could add code coverage, which will help us do the coverage in a single tool.
UI testing should be more in-depth. Right now, they only have one feature: record and play. We need to have a bit more in terms of functionality. We hope they will improve on this in the future.
The summary reports could be improved because sometimes it is not very concise. The waiver process can also be improved because Parasoft SQAtest doesn't have a method to waive off one rule. Additionally, adding some guidance on providing standard templates could be helpful for new engineers or in complexity reduction. It could be sustained in a better way because it currently just gives the number that is a level of looping or callings. Hence, if something can be improved to refactor the code, then it should be code restructuring and all the information that can be provided to look at the complexity of the code.
From an automation point of view, it should have better clarity and be more user friendly. Some aspects were difficult and therefore less useful for us, perhaps we lack the coding knowledge on that.
The product is very slow to start up, and that is a bit of a problem, actually. It is not as fast and it's a bit clunky, especially if you use it for the whole day or for a long time, it doesn't save the data, for example. So, it's a bit clunky and slow.
Reports could be customized and more descriptive according to the user's or company's requirements.