pmd7_2 took 11 seconds to run and found 8 violations
pmd7_3 took 13 seconds to run and found 8 violations
Among the 8 total comparisons:
Violation counts:
# | fileName | line | column | endLine | endColumn | engine | ruleName | severity | category | url | message |
---|---|---|---|---|---|---|---|---|---|---|---|
1 | /ProcessTracker/classes/testAutomationRuntime.cls | 2 | 10 | 42 | 7 | pmd | ClassNamingConventions | 1 | Code Style | https://docs.pmd-code.org/pmd-doc-7.2.0/pmd_rules_apex_codestyle.html#classnamingconventions | The test class name 'testAutomationRuntime' doesn't match '[A-Z][a-zA-Z0-9_]*' |
1 | /ProcessTracker/classes/testAutomationRuntime.cls | 2 | 10 | 42 | 7 | pmd | ClassNamingConventions | 1 | Code Style | https://docs.pmd-code.org/pmd-doc-7.3.0/pmd_rules_apex_codestyle.html#classnamingconventions | The test class name 'testAutomationRuntime' doesn't match '[A-Z][a-zA-Z0-9_]*' |
2 | /ProcessTracker/classes/testAutomationRuntime.cls | 20 | 20 | 42 | 6 | pmd | ApexUnitTestMethodShouldHaveIsTestAnnotation | 3 | Best Practices | https://docs.pmd-code.org/pmd-doc-7.2.0/pmd_rules_apex_bestpractices.html#apexunittestmethodshouldhaveistestannotation | Apex test methods should have @isTest annotation. |
2 | /ProcessTracker/classes/testAutomationRuntime.cls | 20 | 20 | 42 | 6 | pmd | ApexUnitTestMethodShouldHaveIsTestAnnotation | 3 | Best Practices | https://docs.pmd-code.org/pmd-doc-7.3.0/pmd_rules_apex_bestpractices.html#apexunittestmethodshouldhaveistestannotation | Apex test methods should have @isTest annotation. |
3 | /ProcessTracker/classes/testAutomationRuntime.cls | 20 | 20 | 42 | 6 | pmd | MethodNamingConventions | 1 | Code Style | https://docs.pmd-code.org/pmd-doc-7.2.0/pmd_rules_apex_codestyle.html#methodnamingconventions | The test method name 'LaunchFlow' doesn't match '[a-z][a-zA-Z0-9]*' |
3 | /ProcessTracker/classes/testAutomationRuntime.cls | 20 | 20 | 42 | 6 | pmd | MethodNamingConventions | 1 | Code Style | https://docs.pmd-code.org/pmd-doc-7.3.0/pmd_rules_apex_codestyle.html#methodnamingconventions | The test method name 'LaunchFlow' doesn't match '[a-z][a-zA-Z0-9]*' |
4 | /ProcessTracker/classes/testAutomationRuntime.cls | 39 | 9 | 39 | 79 | pmd | ApexAssertionsShouldIncludeMessage | 3 | Best Practices | https://docs.pmd-code.org/pmd-doc-7.2.0/pmd_rules_apex_bestpractices.html#apexassertionsshouldincludemessage | 'System.assertEquals' should have 3 parameters. |
4 | /ProcessTracker/classes/testAutomationRuntime.cls | 39 | 9 | 39 | 79 | pmd | ApexAssertionsShouldIncludeMessage | 3 | Best Practices | https://docs.pmd-code.org/pmd-doc-7.3.0/pmd_rules_apex_bestpractices.html#apexassertionsshouldincludemessage | 'System.assertEquals' should have 3 parameters. |
5 | /ProcessTracker/classes/testAutomationRuntime.cls | 40 | 9 | 40 | 75 | pmd | AvoidDebugStatements | 3 | Performance | https://docs.pmd-code.org/pmd-doc-7.2.0/pmd_rules_apex_performance.html#avoiddebugstatements | Avoid debug statements since they impact on performance |
5 | /ProcessTracker/classes/testAutomationRuntime.cls | 40 | 9 | 40 | 75 | pmd | AvoidDebugStatements | 3 | Performance | https://docs.pmd-code.org/pmd-doc-7.3.0/pmd_rules_apex_performance.html#avoiddebugstatements | Avoid debug statements since they impact on performance |
6 | /ProcessTracker/classes/testAutomationRuntime.cls | 40 | 9 | 40 | 75 | pmd | DebugsShouldUseLoggingLevel | 3 | Best Practices | https://docs.pmd-code.org/pmd-doc-7.2.0/pmd_rules_apex_bestpractices.html#debugsshoulduselogginglevel | Calls to System.debug should specify a logging level. |
6 | /ProcessTracker/classes/testAutomationRuntime.cls | 40 | 9 | 40 | 75 | pmd | DebugsShouldUseLoggingLevel | 3 | Best Practices | https://docs.pmd-code.org/pmd-doc-7.3.0/pmd_rules_apex_bestpractices.html#debugsshoulduselogginglevel | Calls to System.debug should specify a logging level. |
7 | /ProcessTracker/classes/testAutomationRuntime.cls | 41 | 9 | 41 | 74 | pmd | AvoidDebugStatements | 3 | Performance | https://docs.pmd-code.org/pmd-doc-7.2.0/pmd_rules_apex_performance.html#avoiddebugstatements | Avoid debug statements since they impact on performance |
7 | /ProcessTracker/classes/testAutomationRuntime.cls | 41 | 9 | 41 | 74 | pmd | AvoidDebugStatements | 3 | Performance | https://docs.pmd-code.org/pmd-doc-7.3.0/pmd_rules_apex_performance.html#avoiddebugstatements | Avoid debug statements since they impact on performance |
8 | /ProcessTracker/classes/testAutomationRuntime.cls | 41 | 9 | 41 | 74 | pmd | DebugsShouldUseLoggingLevel | 3 | Best Practices | https://docs.pmd-code.org/pmd-doc-7.2.0/pmd_rules_apex_bestpractices.html#debugsshoulduselogginglevel | Calls to System.debug should specify a logging level. |
8 | /ProcessTracker/classes/testAutomationRuntime.cls | 41 | 9 | 41 | 74 | pmd | DebugsShouldUseLoggingLevel | 3 | Best Practices | https://docs.pmd-code.org/pmd-doc-7.3.0/pmd_rules_apex_bestpractices.html#debugsshoulduselogginglevel | Calls to System.debug should specify a logging level. |