-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid code coverage report using sfdx force:source:deploy and force:mdapi:deploy #1568
Comments
Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support. |
Test level was always RunLocalTests |
Hi @bzacharski could you please provide the exact commands and arguments you running? |
@WillieRuemmele |
I've just checked it on 7.156.1 and the issue still exist. @WillieRuemmele were you able to check / reproduce it? |
I dug into this with the person who added all the fancy new coverage stuff to
I know it sucks, but I'm going to close this and call it "working as designed" with full sympathy that the design isn't great. |
Meanwhile, here is a workaround for those who need to check code coverage while calling force:source:deploy :) |
@mshanemc - Is there any updates to the above in regards to fixing how the deploy commands ( My plugin just converts the Basically, I can't update my plugin to report "covered" lines until the Salesforce CLI is updated to correctly return "covered" lines in the coverage JSON output. |
Definitely read the VSCode issue. WI is W-16286380 when you open those magical Support Cases that will get the Apex team's attention ! |
Summary
Tested on version 7.155.0 (salesforce/salesforcedx:7.155.0-full), 154 and 153
I wanted to use code coverage from deploy commands to feed sonarqube (json format) and gitlab (cobertura format) with code coverage information, but it is failing. I've analyzed reports from deploy commands and compared them to reports from force:apex:test:run command.
test:run entry for given class:
deploy json entry for class:
deploy cobertura entry for class:
Steps To Reproduce:
Create class similar to example, deploy to org, run test:run and gather json coverage report, deploy the same class using deploy command (mdapi or source) and gather json and/or cobertura coverage reports
Expected result
Deploy commands produce valid reports. Json reports for tesr:run and deploy commands have similar/identical structure.
Actual result
Reports from deploy commands are invalid. Json reports have different structure.
System Information
Additional information
The text was updated successfully, but these errors were encountered: