Writing test classes to cover both positive, negative, and bulkified scenarios are always the best practices that each developer should follow. While writing test classes, our approach should be to cover as much as code and all the scenarios. There is a restriction from Salesforce that if there is not enough coverage (75%) for the code, then Salesforce will not allow you to deploy your code to production.

So identifying the code coverage is very important. Now there are multiple ways we can get to know the code coverage like – Setup menu, Developer Console, SOQL Query, Salesforce CLI, or Salesforce extension in Visual Studio Code. With so many options there comes the difficulties. Each option presents the code coverage in a different way and more importantly, each option calculates code coverage in a different way. This always creates confusion. For example, when a developer writes the test class and executes that from CLI, it provides the code coverage, let’s say 90%, which should be good enough to deploy the code into Production. But while deployment, the code coverage came down to 50%, and thus deployment stops. The reason for this drop in code coverage is that while deploying code coverage is calculated at the org level i.e. percentage of coverage for that class across the org.

To solve this problem, Salesforce comes up with the Enhanced Code Coverage option. With this option, developer will get – 

• Different classes being covered by the test class. The percentage of each class covered and uncovered lines from each class.
• Test result which will pass/fail result for each test method.
• Finally Test Summary will show “Test Run Coverage” and “Org Wide Coverage”.

Setting up the environment variable

SFDX_IMPROVED_CODE_COVERAGE=true sfdx force:apex:test:run ...

export SFDX_IMPROVED_CODE_COVERAGE=true

Running the test

sfdx force:apex:test:run -n “CommunicationHandlerTest” -c -r human