Skip to content
This repository has been archived by the owner on Mar 18, 2024. It is now read-only.

Inaccurate package coverage percentage on validate #556

Closed
aly76 opened this issue Jun 17, 2021 · 0 comments · Fixed by #560
Closed

Inaccurate package coverage percentage on validate #556

aly76 opened this issue Jun 17, 2021 · 0 comments · Fixed by #560
Assignees
Labels
bug Something isn't working

Comments

@aly76
Copy link
Contributor

aly76 commented Jun 17, 2021

Describe the bug
The package coverage percentage calculated for unlocked packages in orchestrator:validate is inaccurate. Classes and triggers that are not touched by any test class are not accounted for in the calculation of package coverage.

This leads to potential scenarios where an unlocked package satisfies the coverage requirement, despite there being an overwhelming number of classes in the package not touched by the execution of test classes.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
The package coverage calculation should include the lines from classes in the package that have not been touched by any test classes.

Screenshots
If applicable, add screenshots to help explain your problem.

Platform Details (please complete the following information):

  • OS:
  • Version [e.g. CLI Version eg: 1.6.6]
  • Salesforce CLI(sfdx cli) Version:
  • CI Platform:

Additional context
Add any other context about the problem here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants