Which is not part of Code Review with SonarQube?

By Priyanshu Piyush

November 28, 2023

The answer is simple. "Submitted" is not a part of code review with SonarQube. Within the software development lifecycle, code reviews are a key tool to ensure the quality, reliability, and maintenance of the code. In this framework, SonarQube has become an effective tool for static code analysis that gives developers information about possible early-stage problems. It is crucial for teams seeking a reliable and efficient supply of software to understand the elements that the SonarQube covers in technical code assessments.

In this article, we will discuss why "Submitted" is not a part of code review with SonarQube and the reasons not to add it in SonarQube. Moreover, the tools that are parts of code review will also be discussed in this article.


Code Review with SonarQube

A code review is the process of software quality assurance, which systematically examines and evaluates the source code of a program by one or more people or tools. At least one of the people reviewing the code must read the code and identify the problems within the code. The objective of a code review is to identify errors, improve code quality, and follow the best coding standards and practices.

Code reviews are usually carried out before the code is integrated into the main branch of the code base, and to maintain quality over time, you can also periodically perform on existing codes. The code review process helps capture errors at the beginning of the software development life cycle (SDLC), promotes cooperation between team members, and ultimately results in a more reliable and stable software product.

Importance of Code Review

Code review is an important method for improving the quality of software, which can help detect defects and errors, make your code easier to read, improve security and serviceability, and exchange knowledge early in the development process. Code reviews early in the development lifecycle save time and money later in the process.


You can also leverage code reviews early to make it easier for future developers to work on and understand the code they evaluate. This helps facilitate the sharing of code ownership and facilitates knowledge and cooperation among team members.

Elements which are parts of Code Review with SonarQube

Code smells

The code smell is not an error or bug. Instead, it's a complete violation of the software development basics, which reduces the quality of the code.

Code smell indicates a deeper problem, but as its name suggests, it is sniffed or immediately found. The best code smell leads to a problem that is easy to find but interesting. With the help of SonarQube, code smell can easily be detected.


A bug is an error in the source code that causes the program to generate unexpected results or completely conflict with the program. Because coding bugs can affect application performance, developers must ensure that bugs are fixed before selling software to customers. That is why it is part of the code review with SonarQube to maintain tool quality.

Code Duplication

Code Duplication is a common problem in many databases in the software industry. Duplication greatly reduces the chances of maintaining your code. Many projects are declared unqualitative because of excessive duplication, and developers have complained about this state of affairs. SonarQube considered it a necessary part to add to the code review.

Test Coverage

The test coverage is defined as an index in the software test. This includes collecting information about which part of the program was executed when the test suite was executed and determining which branch of the conditional statement was performed.

These tools assure the quality of the test, helping identify what portions of the code were actually touched for the release or fix. They also aid in determining the paths in your application that were not tested.

Why submitted is not a part of Code Review with SonarQube?


This is because the purpose of a code review with SonarQube is to analyze and evaluate the quality of the code rather than simply submitting it for review.

SonarQube focuses on identifying and highlighting potential issues, bugs, vulnerabilities, and code smells within the submitted code. It provides developers with valuable insights and recommendations for improving the overall quality of their codebase.

While "submitted" may not be explicitly mentioned as a part of the technical review process in SonarQube, it is important to understand that submitting your code for analysis is an essential step in leveraging this powerful tool. By doing so, you can gain valuable feedback and insights that will help you enhance your code's reliability, maintainability, and security.

So remember, when using SonarQube for code reviews, focus on analyzing your submitted code rather than expecting a traditional review process where "submitted" plays a specific role.

Drawbacks of submitted in the Code Review

  • Limits the accounting for the specific context or requirements of a project.
  • Use of predefined rules and metrics may not align perfectly with project needs.
  • Potential for the tool to incorrectly flag functional code as problematic.
  • Risk of wasted time and effort in investigating and fixing non-existent issues.
  • Creation of an over-reliance on automated processes may reduce the developers' creativity.
  • Possible overlooking of critical thinking and manual review processes.

SonarQube Limitations

  • False Negatives and Positives: Like any other static code analysis tool, SonarQube can sometimes create an illusion (a problem that is not a problem) or false negatives (a failure to detect a real problem). It is important to review and validate the results of SonarQube so that you do not want to overlook unnecessary rework or real problems.
  • Limited support for some C++ features: : SonarQube may not support some C++ features, such as templates and namespaces, which may limit efficiency.
  • Consolidation: : Integration of SonarQube in the development process can be difficult, and additional time and effort may be required for configuration and setup.


In conclusion, we hope you have found the answer to your question and the reason why Submitted is not a part of code review with SonarQube. SonarQube maintains its tool quality and does want to add, which may cause its users to be disadvantaged. That is why it has not "Submitted" part of its code review, and all the other functions are available for developers to maintain the best code quality.

Share this post :

Subscribe to receive future updates

Never miss a beat by subscribing to receive future updates. Be the first to know about new features, product releases, exciting enhancements, and valuable insights.

No spam guaranteed, So please don’t send any spam mail.