Cost effective way to find and correct issues early
January 18, 2023
Cost effective way to find and correct issues early
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with SonarQube
We use SonarQube as a component in our development and continuous integration environment when developing IT systems. The main purpose of our usage is to be able to identify and find bad design choices and mistakes at an early development stage. Developers use it both in their development environment to be able to find things before committing code and also in the CI environment after committing code to a feature branch but before merging it to master branch.
- Identify bugs in code
- Identify bad design choices in the code
- Give suggestions how to solve bad design choices
- Could provide more configuration templates for suitable warning levels
- Improved possibility to escalate repeated errors to architects and management
- Easy way to deactivate a warning in a specific file
- Integration with CI pipeline
- Integration with development IDE
- Suggestions how to fix identified problems
- Less bugs
- Decreased maintenance thanks to improved code quantity
- Education for less experienced developers
SonarQube identifies significant more thing compared to the built-in suggestions in IntelliJ IDEA. The suggestions how to correct issues are also a lot better with SonarQube. IntelliJ IDEA provides great refactoring support to make it easy to refactor the code to solve issues. We use these tools together and they really complement each other.
Do you think SonarQube delivers good value for the price?
Yes
Are you happy with SonarQube's feature set?
Yes
Did SonarQube live up to sales and marketing promises?
Yes
Did implementation of SonarQube go as expected?
Yes
Would you buy SonarQube again?
Yes