{"id":5787,"date":"2016-11-08T18:01:07","date_gmt":"2016-11-08T18:01:07","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=5787"},"modified":"2016-11-08T18:04:20","modified_gmt":"2016-11-08T18:04:20","slug":"automated-code-review-for-apex-in-salesforce-static-code-analysis-video","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/automated-code-review-for-apex-in-salesforce-static-code-analysis-video\/","title":{"rendered":"Automated Code review for Apex in Salesforce – Static code analysis – Video"},"content":{"rendered":"

PMD is very well known source code analyzer for Java, android and many more languages. Good news for us (Salesforce developers) is , that it supports now Apex<\/a>. You might be thinking how can we make PMD as part of our daily life ?<\/p>\n

There are multiple ways<\/p>\n

    \n
  1. We can run static code analysis standalone<\/li>\n
  2. It can be part of ANT build to generate error reports<\/li>\n
  3. Jenkins <\/a>can use it to generate nice report around code quality<\/li>\n
  4. Eclipse can use it as a plugin to generate report<\/li>\n<\/ol>\n

    In this blog post, we will discuss option 1, that is running it as a standalone application to generate code quality report.<\/p>\n

    First\u00a0Step<\/strong> is to download jar file of latest PMD distribution from here<\/a>.<\/p>\n

    Next step is to define some rules for your code base. Sample rules can be seen here<\/a>. We can also create our\u00a0own rule as per need. For this blog post, I would be using below rules.<\/p>\n

    Apex Rules.xml<\/strong><\/span><\/p>\n

    \r\n<?xml version="1.0"?>\r\n<ruleset name="Apex Rules" xmlns="http:\/\/pmd.sourceforge.net\/ruleset\/2.0.0" xmlns:xsi="http:\/\/www.w3.org\/2001\/XMLSchema-instance" xsi:schemaLocation="http:\/\/pmd.sourceforge.net\/ruleset\/2.0.0 http:\/\/pmd.sourceforge.net\/ruleset_2_0_0.xsd">\r\n\t \r\n\t<rule name="AvoidDeeplyNestedIfStmts" message="Avoid creating deeply nested if-then statements since they are harder to read and error-prone to maintain." class="net.sourceforge.pmd.lang.apex.rule.complexity.AvoidDeeplyNestedIfStmtsRule">\r\n      <description>\r\n      Avoid creating deeply nested if-then statements since they are harder to read and error-prone to maintain.\r\n      <\/description>\r\n        <priority>3<\/priority> \r\n      <example>\r\n\t\t<![CDATA[ public class Foo { public void bar(Integer x, Integer y, Integer z) { if (x>y) {\r\n\t\t\t\t\t\tif (y>z) {\r\n\t\t\t\t\t\t\tif (z==x) {\r\n\t\t\t\t\t\t\t\t\/\/ !! too deep\r\n\t\t\t\t\t\t\t}\r\n\t\t\t\t\t\t}\r\n\t\t\t\t\t}\r\n\t\t\t\t}\r\n\t\t\t}\r\n\t\t]]>\r\n      <\/example>\r\n    <\/rule>\r\n\t\r\n\t<rule name="ExcessiveParameterList" message="Methods with numerous parameters are a challenge to maintain, especially if most of them share the same datatype. These situations usually denote the need for new objects to wrap the numerous parameters." class="net.sourceforge.pmd.lang.apex.rule.complexity.ExcessiveParameterListRule">\r\n      <description>\r\n      Methods with numerous parameters are a challenge to maintain, especially if most of them share the same datatype. These situations usually denote the need for new objects to wrap the numerous parameters.\r\n      <\/description>\r\n        <priority>3<\/priority> \r\n      <example>\r\n\t\t<![CDATA[ \r\n\/\/ too many arguments liable to be mixed up \r\npublic void addPerson(int birthYear, int birthMonth, int birthDate, int height, int weight, int ssn) \r\n{ ... } \r\n\r\n\/\/ preferred approach public void addPerson(Date birthdate, BodyMeasurements measurements, int ssn) \r\n{ ... } \r\n]]>\r\n      <\/example>\r\n    <\/rule>\r\n\t\r\n\t <rule name="ExcessiveClassLength" message="Excessive class file lengths are usually indications that the class may be burdened with excessive responsibilities that could be provided by external classes or functions. In breaking these methods apart the code becomes more managable and ripe for reuse." class="net.sourceforge.pmd.lang.apex.rule.complexity.ExcessiveClassLengthRule">\r\n      <description>\r\n      Excessive class file lengths are usually indications that the class may be burdened with excessive responsibilities that could be provided by external classes or functions. In breaking these methods apart the code becomes more managable and ripe for reuse.\r\n      <\/description>\r\n        <priority>3<\/priority> \r\n      <example>\r\n\t\t<![CDATA[ \r\npublic class Foo { public void bar(Integer x, Integer y, Integer z) { if (x>y) {\r\n\t\t\t\t\t\tif (y>z) {\r\n\t\t\t\t\t\t\tif (z==x) {\r\n\t\t\t\t\t\t\t\t\/\/ !! too deep\r\n\t\t\t\t\t\t\t}\r\n\t\t\t\t\t\t}\r\n\t\t\t\t\t}\r\n\t\t\t\t}\r\n\t\t\t}\r\n\t\t]]>\r\n      <\/example>\r\n    <\/rule>\r\n\t\r\n\t<rule name="NcssMethodCount" message="This rule uses the NCSS (Non-Commenting Source Statements) algorithm to determine the number of lines of code for a given method. NCSS ignores comments, and counts actual statements. Using this algorithm, lines of code that are split are counted as one." class="net.sourceforge.pmd.lang.apex.rule.complexity.NcssMethodCountRule">\r\n      <description>\r\n      This rule uses the NCSS (Non-Commenting Source Statements) algorithm to determine the number of lines of code for a given method. NCSS ignores comments, and counts actual statements. Using this algorithm, lines of code that are split are counted as one.\r\n      <\/description>\r\n        <priority>3<\/priority> \r\n      <example>\r\n\t\t<![CDATA[ \r\npublic class Foo extends Bar \r\n{ \r\n\/\/this method only has 1 NCSS lines \r\npublic Integer methd() { \r\nsuper.methd(); \r\nreturn 1; \r\n} } \r\n]]>\r\n      <\/example>\r\n    <\/rule> \r\n<\/ruleset>\r\n<\/pre>\n
    In above sample rule file, if we observe carefully, each rule is represented by\u00a0rule<\/strong> tag. we can give it any\u00a0name\u00a0<\/strong>and then\u00a0message\u00a0<\/strong>to be displayed in report.\u00a0class<\/strong> represents respective rule written in Java class by PMD and this information would be available here<\/a>.<\/p>\n
    priority<\/strong> can set level of violations and this would differ as per your project. We can categorize level of violations for each rule and it helps us in reporting code quality of developer team.<\/p>\n
    Final step is to run below command from shell \/ command prompt. This documentation<\/a> will help to understand all parameters needed to run PMD from command prompt.<\/p>\n
    \r\npmd -d "path of folder where all apex files exists" -f html -R "path of rule file in our case above file ApexRules.xml" -reportfile "path of report to be generated"\r\n<\/pre>\n
    Following image shows sample command run<\/p>\n
    \"Sample<\/a>
    Sample command to run PMD from console<\/figcaption><\/figure>\n
    Below is\u00a0sample code quality report generated<\/p>\n
    \"Apex<\/a>
    Apex code quality report<\/figcaption><\/figure>\n
    Youtube video<\/strong><\/p>\n