What is our primary use case?
I use Coverity in my company mainly to fix bug issues and detect errors with code analysis.
How has it helped my organization?
The ability of Coverity to fix bug issues is important to me. Coverity actually helps to debug and deal really fast when it comes to code analysis. Coverity does have a higher detection rate. It is easy to integrate Coverity into the CI/CD pipeline. Coverity is helpful in marking false positives. Though Coverity has some pros and cons, its pros make it a quite good tool.
What is most valuable?
The scanning ability of Coverity is good since it helps fix bug issues. The interface of Coverity is quite good, and it is also easy to use.
What needs improvement?
Coverity takes a lot of time to dereference null pointers. The product's price is one of its shortcomings, where improvements are required. In general, the price of the product should be kept low.
In the future, Coverity should provide more flexibility.
For how long have I used the solution?
I have been using Coverity for a year. I use the solution's latest version. I am a customer of the tool.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a seven out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution an eight out of ten. I rate the coverage of the product a six out of ten.
Currently, five people in my company use Coverity. My company plans to increase the use of the tool for twenty people.
How are customer service and support?
The solution's technical support is good. I rate the technical support a nine out of ten.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have experience with SonarQube. I switched to Coverity from SonarQube since the former mainly focuses on scanning and detection of bugs, while the latter focuses on the security of the code. If you want only to fix bugs, then the focus of the product should also be quite good, like Coverity. SonarQube's focus area is different from Coverity.
How was the initial setup?
I rate the initial setup of Coverity an eight on a scale of one to ten, where one is difficult, and ten is easy.
The setup phase of Coverity can sometimes be straightforward, and if there are some issues, it can be a little bit complex. When involved in some tracking activity, sometimes, Coverity uses looping logic, making it quite difficult to handle bugs. Sometimes, the tracking activity in Coverity will be straightforward with a very good interface. Marking the positive rates and giving some green and red bars can be helpful in Coverity.
The solution is deployed on an on-premises model.
The solution can be deployed in a day.
My company uses the git repository for the implementation of Coverity.
Five people are required to deploy the solution. Around thirty people might be required to take care of the maintenance process of the product since there will be an increase in the team members in our company.
What was our ROI?
I haven't seen any return on investment from the use of Coverity.
What's my experience with pricing, setup cost, and licensing?
Coverity's cost is quite high. Coverity costs for a year are too high. I rate Coverity's price a ten on a scale of one to ten, where one is cheap and ten is expensive. There are no additional costs apart from the licensing costs attached to the product.
Which other solutions did I evaluate?
Though my company had other options apart from Coverity, we chose to continue with Coverity as we were already using it for some projects in our organization.
What other advice do I have?
Coverity is quite a good tool that helps fix big issues and deal with code analysis. Coverity's scanning features and scalability are also quite good. The only drawback of the product stems from the fact that it is quite an expensive product. The product's cost can seem too high for a normal user. If your organization is quite good and okay with exploring the tool with its current costs, then you can opt for Coverity. Otherwise, you can use other solutions, like the free community edition from SonarQube.
I rate the overall solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.