BACK TO LIST

Apex rules

All the static analysis rules you need for the Salesforce APEX language. Use Codiga to analyze your code and automate your code reviews for APEX.

ApexUnitTestClassShouldHaveAsserts

Best practice
Warning

Apex unit test classes should have at least one System.assert() or assertEquals() or AssertNotEquals() call

Learn more

AvoidGlobalModifier

Best practice
Warning

Avoid using global modifier

AvoidLogicInTrigger

Best practice
Warning

Avoid logic in triggers

DebugsShouldUseLoggingLevel

Best practice
Warning

Calls to System.debug should specify a logging level.

NcssConstructorCount

Best practice
Warning

The constructor has a high NCSS line count

NcssTypeCount

Best practice
Warning

The type has a high NCSS line count

ApexUnitTestShouldNotUseSeeAllDataTrue

Best practice
Warning

Apex unit tests should not use @isTest(seeAllData=true) because it opens up the existing database data for unexpected modification by tests.

ApexXSSFromURLParam

Best practice
Error

Apex classes should escape Strings obtained from URL parameters

We use cookies to improve your site experience, including analytics cookies to understand how you use our product and design better experiences. Please read our Cookie Policy.