We performed a comparison between Klocwork and Parasoft SOAtest based on real PeerSpot user reviews.
Find out in this report how the two Static Application Security Testing (SAST) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The tool helps the team to think beforehand about corner cases or potential bugs that might arise in real-time."
"The most valuable feature is the Incremental analysis."
"The most valuable feature of Klocwork is finding defects while you're doing the coding. For example, if you have an IDE plug-in of Klocwork on Visual Studio or Eclipse, you can find the faults; similar to using spell check on Word, you can find out defects during the development phase, which means that you don't have to wait till the development is over to find the flaws and address the deficiencies. I also find language support in Klocwork good because it used to support only C, C++, C#, and Java, but now, it also supports Java scripts and Python."
"We like using the static analysis and code refactoring, which are very valuable because of our requirements to meet safety critical levels and reliability."
"It's integrated into our CI, continuous integration."
"Technical support is quite good."
"I like not having to dig through false positives. Chasing down a false positive can take anywhere from five minutes for a small easy one, then something that is complicated and goes through a whole bunch of different class cases, and it can take up to 45 minutes to an hour to find out if it is a false positive or not."
"The ability to create custom checkers is a plus."
"The testing time is shortened because we generate test data automatically with SOAtest."
"If you want something that’s not provided out of the box, then you can write it yourself and integrate it with SOAtest."
"They have a feature where they can record traffic and create tests on the report traffic."
"Automatic testing is the most valuable feature."
"Since the solution has both command line and automation options, it generates good reports."
"Parasoft SOAtest has improved the quality of our automated web services, which can be easily implemented through service chaining and service virtualization."
"Technical support is helpful."
"The solution is scalable."
"We'd like to see integration with Agile DevOps and Agile methodologies."
"I believe it should support more languages, such as Python and JavaScript."
"This solution could be improved if they offered support of more languages including Ada and Golang. They currently only support seven languages."
"Under NIST cybersecurity standards, we must address vulnerabilities within a specified time after discovering them. When we try to propagate those updates and fixes through the system, it would be nice if the clients could reconnect to the existing server or have the server dynamically updated in some way. I know that isn't easy, but maybe processes could be enhanced to make that more streamlined from a DevOps perspective."
"We bought Klocwork, but it was limited to one little program, but the program is now sort of failing. So, we have a license for usage on a program that is sort of failing, and we really can't use the license on anything else."
"Klocwork has to improve its features to stay ahead of other free solutions."
"Klocwork does have a problem with true positives. It only found 30% of true positives in the Juliet test case."
"The way to define the rules is too complex. The definition/rules for static analysis could be automated according to various SILs, so as to avoid confusion."
"The summary reports could be improved."
"Compatibility with HTTP 1.1 and TLS 1.2 needs to be improved."
"From an automation point of view, it should have better clarity and be more user friendly."
"Enabling/disabling an optional element of an XML request is only possible if a data source (e.g., Excel sheet) is connected to the test. Otherwise, the option is not available at all in the drop-down menu."
"UI testing should be more in-depth."
"Reports could be customized and more descriptive according to the user's or company's requirements."
"Tuning the tool takes time because it gives quite a long list of warnings."
"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."
Klocwork is ranked 12th in Static Application Security Testing (SAST) with 20 reviews while Parasoft SOAtest is ranked 29th in Static Application Security Testing (SAST) with 30 reviews. Klocwork is rated 8.2, while Parasoft SOAtest is rated 8.2. The top reviewer of Klocwork writes "Their technical team helps us get the most out of the solution, but we've faced some stability problems in our environment". On the other hand, the top reviewer of Parasoft SOAtest writes "Good API testing and RIT feature; clarity could be improved". Klocwork is most compared with SonarQube, Coverity, Polyspace Code Prover, Checkmarx One and Fortify on Demand, whereas Parasoft SOAtest is most compared with Postman, SonarQube, Coverity, Polyspace Code Prover and Fortify on Demand. See our Klocwork vs. Parasoft SOAtest report.
See our list of best Static Application Security Testing (SAST) vendors.
We monitor all Static Application Security Testing (SAST) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.