ApexUnitTestClassShouldHaveAsserts
Best practice
Warning
Apex unit test classes should have at least one System.assert() or assertEquals() or AssertNotEquals() call
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.
Apex unit test classes should have at least one System.assert() or assertEquals() or AssertNotEquals() call
Avoid using global modifier
Avoid logic in triggers
Calls to System.debug should specify a logging level.
The constructor has a high NCSS line count
The type has a high NCSS line count
Apex unit tests should not use @isTest(seeAllData=true) because it opens up the existing database data for unexpected modification by tests.
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.