You are using SonarQube and its Java Analyzer to analyze your projects, but there aren't rules that allow you to target some of your company's specific needs? Then your logical choice may be to implement your own set of custom Java rules.
This document is an introduction to custom rule writing for the SonarQube Java Analyzer. It will cover all the main concepts of static analysis required to understand and develop effective rules, relying on the API provided by the SonarQube Java Plugin.
The rules you are going to develop will be delivered using a dedicated, custom plugin, relying on the SonarQube Java Plugin API. In order to start working efficiently, we provide a empty template maven project, that you will fill in while following this tutorial.
Grab the template project from there and import it to your IDE: https://github.com/SonarSource/sonar-custom-rules-examples/tree/master/java-custom-rules
This project already contains custom rules. Our goal will be to add an extra rule!
Looking at the pom
A custom plugin is a Maven project, and before diving into code, it is important to notice a few relevant lines related to the configuration of your soon-to-be-released custom plugin.
In the code snippet below, note the plugin API version (
<sonar.version>) provided through the properties. It relates to the minimum version of SonarQube your plugin will support, and is generally aligned to your company's SonarQube instance. In this template, we rely on the version 6.0 (LTS version is 5.6, but compatibility is guaranteed when packaging the plugin). Note that latest released versions of the Java Analyzer are always compatible with the current LTS version of SonarQube.
<java.plugin.version> is the minimum version of the Java Analyzer that will be required to run your custom plugin in your SonarQube instance. Consequently, as we will rely on version 18.104.22.16898 of the Java plugin, the SonarQube instance which will use the custom plugin will need version 22.214.171.12498 of the Java Plugin as well.
For the moment, don't touch these two properties.
Other properties such as
<description> can be freely modified.
In the code snippet below, it is important to note that the entry point of the plugin is provided as the
<pluginClass> in the configuration of the
sonar-packaging-maven plugin, using the fully qualified name of the java class
MyJavaRulesPlugin. If you refactor your code, rename, or move the class extending
org.sonar.api.SonarPlugin, you will have to change this configuration. It's also the property
<sonarQubeMinVersion> which guarantees the compatibility with LTS 5.6.
Writing a rule
In this section we will write a custom rule from scratch. To do so, we will use a Test Driven Development (TDD) approach, relying on writing some test cases first, followed by the implementation a solution.
Three files to forge a rule
When implementing a rule, there is always a minimum of 3 distinct files to create:
- A test file, which contains Java code used as input data for testing the rule
- A test class, which contains the rule's unit test
- A rule class, which contains the implementation of the rule.
To create our first custom rule (usually called a "check"), let's start by creating these 3 files in the template project, as described below:
/src/test/files, create a new empty file named
MyFirstCustomCheck.java, and copy-paste the content of the following code snippet.
/src/test/java, create a new test class called
MyFirstCustomCheckTestand copy-paste the content of the following code snippet.
/src/main/java, create a new class called
IssuableSubscriptionVisitorprovided by the Java Plugin API. Then, replace the content of the
nodesToVisit()method with the content from the following code snippet (you may have to import
ImmutableList). This file will be described when dealing with implementation of the rule!
More files ?
If the 3 files described above are always the base of rule writing, there are situations where extra files may be needed. For instance, when a rule uses parameters, or if its behavior relies on the detected version of java, multiple test files could be required. It is also possible to use external files to describe rule metadata, such as a description in html format. Such situations will be described in other topics of this documentation.
A specification to make it right
Of course, before going any further, we need a key element in rule writhing, a specification! For the sake of the exercise, lets consider the following quote from a famous Guru as being the specification of our custom rule, as it is of course absolutely correct and incontrovertible.
A test file to rule them all
Because we chose a TDD approach, the first thing to do is to write examples of the code our rule will target. In this file, we consider numerous cases that our rule may encounter during an analysis, and flag the lines which will require our implementation to raise issues. The flag to be used is a simple "
// Noncompliant" trailing comment on the line of code where an issue should be raised. Why Noncompliant? Because the flagged lines do not comply with the rule.
Covering all the possible cases is not necessarily required, the goal of this file is to cover all the situations which may be encountered during an analysis, but also to abstract irrelevant details. For instance, in the context of our first rule, the name of method, the content of its body, and the owner of the method make no difference, whether it's an abstract class, a concrete class, or an interface. Note that this sample file does not need to be compilable, but it should be structurally correct.
In the test file
MyFirstCustomCheck.java created earlier, copy-paste the following code:
The test file now contains the following test cases:
- line 2: A constructor, to differentiate the case from a method;
- line 4: A method without parameter (foo1);
- line 5: A method returning void (foo2);
- line 6: A method returning the same type as its parameter (foo3), which will be noncompliant;
- line 7: A method with a single parameter, but a different return type (foo4);
- line 8: Another method with a single parameter and same return type, but with non-primitive types (foo5), therefore non compliant too;
- line 10: A method with more than 1 parameter (foo6);
- line 11: A method with a variable arity argument (foo7);
A test class to make it pass
Once the test file is updated, let's update our test class to use it, and link the test to our (not yet implemented) rule. To do so, get back to our test class
MyFirstCustomCheckTest, and update the
test() method as shown in the following code snippet (you may have to import class
As you probably noticed, this test class contains a single test, the purpose of which is to verify the behavior of the rule we are going to implement. To do so, it relies on usage of the
JavaCheckVerifier class, provided by the Java Plugin rule testing API. This
JavaCheckVerifier class provides useful methods to validate rule implementations, allowing us to totally abstract all the mechanisms related to analyzer initialization. Note that while verifying a rule, the verifier will collect lines marked as being Noncompliant, and verify that the rule raises the expected issues and only those issues.
Now, let's proceed to the next step of TDD: make the test fail!
To do so, simply execute the test from the test file using JUnit. The test should fail with error message "At least one issue expected", as shown in the code snippet below. Since our check is not yet implemented, no issue can be raised yet, so that's the expected behavior.
1st version – Using syntax trees and API basics
Before we start with the implementation of the rule itself, you need a little background.
Prior to running any rule, the SonarQube Java Analyzer parses a given Java code file and produces an equivalent data structure: the Syntax Tree. Each construction of the Java language can be represented with a specific kind of Syntax Tree, detailing each of its particularities. Each of these constructions is associated with a specific Kind as well as an interface explicitly describing all its particularities. For instance, the kind associated to the declaration of a method will be
org.sonar.plugins.java.api.tree.Tree.Kind.METHOD, and its interface defined by
org.sonar.plugins.java.api.tree.MethodTree. All the kinds are listed in the the
Kind enum of the Java Plugin.
When creating the rule class, we chose to implement the
IssuableSubscriptionVisitor class from the API. This class, on top of providing a bunch of useful methods to raise issues, also defines the strategy which will be used when analyzing a file. As its name is telling us, it is based on a subscription mechanism, allowing to specify on what kind of tree the rule should react. The list of node types to cover is specified through the
nodesToVisit() method. In the previous steps, we modified the implementation of the method to return an empty list, therefore not subscribing to any node of the syntax tree.
Now its finally time to jump in to the implementation of our first rule! Go back to the
MyFirstCustomCheck class, and modify the list of
Kinds returned by the
nodesToVisit() method. Since our rule targets method declarations, we only need to visit methods. To do so, simply add
Kind.METHOD as a parameter of the returned immutable list, as shown in the following code snippet.
Once the nodes to visit are specified, we have to implement how the rule will react when encountering method declarations. To do so, override method
visitNode(Tree tree), inherited from
Because we registered the rule to visit Method nodes, we know that every time the method is called, the tree parameter will be a
org.sonar.plugins.java.api.tree.MethodTree (the interface tree associated with the
METHOD kind). As a first step, we can consequently safely cast the tree directly into a
MethodTree, as shown below. Note that if we had registered multiple node types, we would have to test the node kind before casting by using the method
Tree.is(Kind ... kind).
Now, let's narrow the focus of the rule by checking that the method has a single parameter, and raise an issue if it's the case.
reportIssue(Tree tree, String message) from
IssuableSubscriptionVisitor allows to report an issue on a given tree with a specific message. In this case, we chose to report the issue at a precise location, which will be the name of the method.
Now, let's test our implementation by executing
Of course, our test failed again... The
JavaCheckVerifier reported that lines 5, 7 and 11 are raising unexpected issues, as visible in the stack-trace above. By looking back at our test file, it's easy to figure out that raising an issue line 5 is wrong because the return type of the method is void, line 7 is wrong because
Object is not the same as
int, and line 11 is also wrong because of the variable arity of the method. Raising these issues is however correct accordingly to our implementation, as we didn't check for the types of the parameter and return type. To handle type, however, we will need to rely on more that what we can achieve using only knowledge of the syntax tree. This time, we will need to use the semantic API!
IssuableSubscriptionVisitor and BaseTreeVisitor
For the implementation of this rule, we chose to use an
IssuableSubscriptionVisitor as the implementation basis of our rule. This visitor offers an easy approach to writing quick and simple rules, because it allows us to narrow the focus of our rule to a given set of
Kinds to visit by subscribing to them. However, this approach is not always the most optimal one. In such a situation, it could be useful to take a look at another visitor provided with the API:
BaseTreeVisitor contains a
visit() method dedicated for each and every kind of the syntax tree, and is particularly useful when the visit of a file has to be fine tuned.
In rules already implemented in the Java Plugin, you will be able to find multiple rule using both approaches: An IssuableSubscriptionVisitor as entry point, helped by simple
BaseTreeVisitor(s) to identify pattern in other parts of code.
2nd version – Using semantic API
Up to now, our rule implementation only relied on the data provided directly by syntax tree that resulted from the parsing of the code. However, the SonarAnalyzer for Java provides a lot more regarding the code being analyzed, because it also construct a semantic model of the code. This semantic model provides information related to each symbol being manipulated. For a method, for instance, the semantic API will provide useful data such as a method's owner, its usages, the types of its parameters and its return type, the exception it may throw, etc. Don't hesitate to explore the semantic package of the API in order to have an idea of what kind of information you will have access to during analysis!
But now, let's go back to our implementation and take advantage of the semantic.
Once we know that our method has a single parameter, let's start by getting the symbol of the method using the
symbol() method from the
From the symbol, it is then pretty easy to retrieve the type of its first parameter, as well as the return type (You may have to import
Since the rule should only raise an issue when these two types are the same, we then simply test if the return type is the same as the type of the first parameter using method
is(String fullyQualifiedName), provided through the
Type class, before raising the issue.
Now, execute the test class again.
Test passed? If not, then check if you somehow missed a step.
If it passed...
Registering the rule in the custom plugin
OK, you are probably quite happy at this point, as our first rule is running as expected... However, we are not really done yet. Before playing our rule against any real projects, we have to finalize its creation within the custom plugin, by registering it.
The first thing to do is to provide to our rule all the metadata which will allow us to register it properly in the SonarQube platform. To do so, add the
org.sonar.check.Rule annotation to
MyFirstCustomCheck class rule, and provide a key, a name, a description and optional tags, as in the following code snippet.
The second things to to is to activate the rule within the plugin. To do so, open class
org.sonar.samples.java.RulesList). In this class, you will notice methods
GetJavaTestChecks(). These methods are used to register our rules with alongside the rule of the Java plugin. Note that rules registered in
GetJavaChecks() will only be played against source files, while rules registered in
GetJavaTestChecks() will only be played against test files. To register the rule, simply add the rule class to the list builder, as in the following code snippet:
Because your rules are relying on the SonarJava API, you also need to tell the SonarJava parent plugin that some new rules have to be retrieved. If you are using the template custom plugin as a base of this tutorial, you should have everything done already, but feel free to have a look at the
MyJavaFileCheckRegistrar.java class, which connects the dots. Finally, be sure that this registrar class is also correctly added as an extension for your custom plugin, by adding it to your Plugin definition class (
Testing a custom plugin
For this chapter, you will need a local instance of SonarQube. If you don't have a SonarQube platform installed on your machine, now is time to download its latest version from HERE!
At this point, we've completed the implementation of a first custom rule and registered it into the custom plugin. The last remaining step is to test it directly with the SonarQube platform and try to analyse a project!
Start by building the project using maven:
Then, grab the jar file
java-custom-rules-1.0-SNAPSHOT.jar from the
target folder of the project, and move it to the extensions folder of your SonarQube instance, which will be located at
SonarQube Java Plugin compatible version
Before going further, be sure to have the adequate version of the SonarQube Java Plugin with your SonarQube instance. The dependency over the Java Plugin of our custom plugin is defined in its
pom, as seen in the first chapter of this tutorial.
If you have a fresh install or do not possess the same version, install the adequate version of the Java Plugin. The latest version of the plugin can be downloaded from HERE.
Now, (re-)start your SonarQube instance, log as admin and navigate to the Rules tab.
From there, under the language section, select "Java", and then "MyCompany Custom Repository" under the repository section. Your rule should now be visible (with all the other sample rules).
Select the rule and activate it in the default quality profile.
Once activated, the only step remaining is to analyse one of your project!
When encountering a method returning the same type as its parameter, the issue will now raise issue, as visible in the following picture:
How to Define Rule Parameters
You have to add a @RuleProperty to your Rule. Check this example : https://github.com/SonarSource/sonar-custom-rules-examples/blob/master/java-custom-rules/src/main/java/org/sonar/samples/java/checks/SecurityAnnotationMandatoryRule.java
How to Test Sources requiring External Binaries
In the pom.xml, define in the Maven Dependency Plugin all the JARs you need to run your Unit Tests. For example, if you sample code used in your Unit Tests is having a dependency on Spring, add it there.
How to Test Precise Issue Location
You can raise an issue on a given line, but you can also raise it at a specific Token. Because of that, you may want to specify, in your sample code used by your Unit Tests, the exact location, i.e. in between which 2 specific Columns, where you are expecting the issue to be raised.
This can be achieved using the special keywords '
sc' (start-column) and '
ec' (end-column) in the "Noncompliant" comment. In the following example, we are expecting to have the issue being raised between the column 27 and 32 (i.e. exactly on "Order" variable type):
SonarQube Platform: http://www.sonarqube.org/
SonarQube Java Plugin Github repository: https://github.com/SonarSource/sonar-java