Salesforce DX Developer Guide

How Salesforce Developer Experience (DX) Tooling Changes the Way You Work
Provide Developers Access to Salesforce DX Tools
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Track Changes Between Your Project and Org
Work with Data
Salesforce DX MCP Server and Tools
Development
Build and Release Your App
Unlocked Packages
What’s an Unlocked Package?
Package-Based Development Model
Before You Create Unlocked Packages
Know Your Orgs
Create Org-Dependent Unlocked Packages
Workflow for Unlocked Packages
Configure Unlocked Packages
How We Handle Profile Settings in Unlocked Packages
Develop Unlocked Packages
Create and Update an Unlocked Package
Create New Versions of an Unlocked Package
Guidance for Package Version Numbering
Code Coverage for Unlocked Packages
Considerations for Promoting Packages with Dependencies
Release an Unlocked Package
Update an Unlocked Package Version
Hard-Deleted Components in Unlocked Packages
Delete an Unlocked Package or Package Version
View Package Details
Push a Package Upgrade for Unlocked Packages
Install an Unlocked Package
Migrate Deprecated Metadata from Unlocked Packages
Uninstall an Unlocked Package
Transfer an Unlocked Package to a Different Dev Hub
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Code Coverage for Unlocked Packages

Before you can promote and release an unlocked package, the Apex code must meet a minimum 75% code coverage requirement. You can install package versions that don't meet code coverage requirements only in scratch orgs and sandboxes.

Unlocked package versions that were promoted to the released state before Winter ‘21 aren’t subject to code coverage requirements.

Important

To compute code coverage using Salesforce CLI, use the --code-coverage parameter when you run the sf package version create command.

Package version creation can take longer to complete when code coverage is being computed, so consider when in the development cycle to include the code coverage parameter. You can choose to skip code coverage, and you can skip all validation by specifying the --skip-validation parameter. You can promote package versions only if they’re validated and meet code coverage requirements.

View code coverage information for a package version using sf package version list with the --verbose parameter, or the sf package version report command in Salesforce CLI.

We don’t calculate code coverage for org-dependent unlocked packages.