Salesforce DX Developer Guide

How Salesforce Developer Experience Changes the Way You Work
Salesforce CLI Configuration and Tips
Project Setup
Authorization
Metadata Coverage
Scratch Orgs
Sandboxes
Development
Build and Release Your App
First-Generation Managed Packages
Second-Generation Managed Packages
Unlocked Packages
What’s a Package
Package-Based Development Model
Before You Create Unlocked Packages
Know Your Orgs
Create Org-Dependent Unlocked Packages (Beta)
Workflow for Unlocked Packages
Configure Packages
Create a Package
Generate the Package
Generate a Package Version
Code Coverage for Unlocked Packages
Release an Unlocked Package
Update a Package Version
View Package Details
Push a Package Upgrade (Beta)
Install a Package
Migrate Deprecated Metadata from Unlocked Packages
Uninstall a Package
Continuous Integration
Troubleshoot Salesforce DX
Limitations for Salesforce DX
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Code Coverage for Unlocked Packages

Although code coverage isn’t enforced for unlocked packages, it’s a best practice to include Apex tests in your unlocked packages.

Starting in Winter ‘21, a minimum 75% code coverage is required for package version promotion. Package versions created in Winter ‘21 and later, that don’t meet this code coverage, can only be installed in scratch orgs and sandboxes. Unlocked package versions that are promoted to the released state before Winter ‘21 won’t be subject to code coverage requirements.

Important

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

Package version creation may take longer to complete when code coverage is being computed, so consider when to include the code coverage parameter.

View code coverage information for a package version using force:package:version:list with the --verbose parameter, or force:package:version:reportcommand in Salesforce CLI.