How to Check Salesforce Apex Code Coverage in Visual Studio Code: A Step-by-Step Guide
Summary
Salesforce teams can manage Apex code quality by checking code coverage directly inside Visual Studio Code using Salesforce Extensions. This guide explains how to enable coverage retrieval, run Apex tests through various methods, and visualize line-by-line coverage results with red and green highlights. It also clarifies the difference between code coverage and test coverage, emphasizing best practices beyond the mandatory 75% coverage threshold. Using these steps and visual feedback helps developers and architects ensure comprehensive test coverage and higher code quality efficiently within their IDE workflow.
Takeaways
- Enable 'Retrieve Test Code Coverage' setting in VS Code before running tests.
- Run Apex tests via context menu, command palette, or Salesforce CLI.
- Use the status bar toggle to view green/red line coverage highlights.
- Understand the difference between code coverage (white-box) and test coverage (black-box).
- Aim for comprehensive test scenarios, not just the minimum 75% coverage.
Introduction For Salesforce professionals—whether you are a Developer, Architect, or technical Admin—managing code quality is non-negotiable. Code coverage is a crucial metric in Salesforce development, with a minimum of 75% coverage required for Apex code deployment to production environments. While you can check these metrics in the Developer Console, modern workflows favor the power of the IDE. You can check and visualize this coverage directly within Visual Studio Code (VS Code) using the official Salesforce Extensions. This guide will walk you through the configuration and execution steps to view your coverage in real-time. Viewing Code Coverage in VS Code To enable and view code coverage highlighting in VS Code, you need to adjust a specific setting and then execute your tests. Here is how to configure your environment. 1. Enable the Setting Before running your tests, ensure your IDE is configured to retrieve coverage data.