---
schema_version: "1"
id: 96e647293afc89b65b7ed154d9bd97eed0ac8d93584f0c739165c70ac57336f8
title: Code Coverage for Second-Generation Managed Packages
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/second-generation/sfdx-dev-dev2gp-code-coverage.md
canonical_url: https://developer.salesforce.com/docs/platform/pkg2-dev/guide/sfdx-dev-dev2gp-code-coverage.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 8abcb822c7570bd68e9bc4439a9aeb1c9af937703f6a6c55f37c2a286dbf0fb2
products:
  - Second-Generation Managed Packaging Developer Guide
  - merged-docs
---

# Code Coverage for Second-Generation Managed Packages

Before you can release and distribute a second-generation managed package version on AgentExchange, the Apex code must meet a minimum 75% code coverage requirement. And every Apex Trigger in a package needs test coverage.

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

Package version creation often takes longer to complete when code coverage is being computed, so consider when to include the code coverage parameter. You can create beta package versions without computing code coverage, but these beta versions can’t be promoted.

If you try to promote a beta package version to managed-released and the version was created without specifying code coverage, or the code coverage in the package version is less than 75%, the package promotion fails. Code coverage is calculated during package version validation. If you skip validation using the `--skip-validation` parameter, code coverage isn’t calculated for that package version.

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