Apex Code Coverage: Avoid Meaningless Test Statements to Inflate Coverage Ratio

Why Meaningless Test Statements Are a Problem

In Apex code development, we don't recommend increasing your org's code coverage ratio by intentionally creating Apex classes or methods containing meaningless, redundant statements — for example, unnecessary variable assignments or repeated calculations that aren't actually used by your application.

If code deployed to production skips a test that should have been run, these meaningless statements can cause unintended behavior or issues. They also skew the true upper limit of Apex characters used in your org, since the code technically counts toward your character limit without providing real test value.

What Salesforce May Ask For

When Salesforce reviews your org's Apex character upper limit, we look at the details behind that number. If meaningless statements are found inflating your code coverage, Salesforce may ask you to modify the Apex code to remove them.