Skip to content
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

Remove empty failure tag on successful test execution #2076

Closed
roftone opened this issue Apr 17, 2023 · 12 comments
Closed

Remove empty failure tag on successful test execution #2076

roftone opened this issue Apr 17, 2023 · 12 comments

Comments

@roftone
Copy link

roftone commented Apr 17, 2023

Is your feature request related to a problem? Please describe.
Yes, new deployment commands seems to have changed the junit xml format. Before, an empty failure tag was not present on the returned xml.

What are you trying to do
Run a mock deployment on a gitlab merge request.

Describe the solution you'd like
Not have the test results be considered a failure.

Describe alternatives you've considered
Reverting to the previous sfdx commands.

Additional context

Before:
image

After:
image

@roftone roftone added the feature Issue or pull request for a new feature label Apr 17, 2023
@github-actions
Copy link

Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming or sprint planning session. We prioritize feature requests with more upvotes and comments.

@git2gus
Copy link

git2gus bot commented Apr 17, 2023

This issue has been linked to a new work item: W-13048665

@WillieRuemmele
Copy link
Member

Hey @roftone 👋 thanks for reporting this,

can you provide some more information such as CLI version and command with flags that you're running, when did you first notice this change?

@roftone
Copy link
Author

roftone commented Apr 17, 2023

Yes,

sfdx-cli 7.196.8 (core)

The command is:
sfdx project deploy start $packageParams $postDestructiveParams --dry-run --wait 3600 --verbose --junit --results-dir ./tests/apex -l RunLocalTests --coverage-formatters json

I had tested the new commands locally and everything seemed fine. It was only today, when I pushed the pipeline change, that I noticed the change in the merge request test results and compared the generated junit files.

@WillieRuemmele
Copy link
Member

great, and does it work correctly if you use sfdx force source deploy?

@WillieRuemmele WillieRuemmele removed the feature Issue or pull request for a new feature label Apr 17, 2023
@WillieRuemmele
Copy link
Member

^ more of a bug, but the WI has already been created

@roftone
Copy link
Author

roftone commented Apr 18, 2023

great, and does it work correctly if you use sfdx force source deploy?

Yes, that's the command that we are using again.

@R0Wi
Copy link

R0Wi commented May 9, 2023

salesforcecli/plugin-deploy-retrieve#610 should fix this. Cheers.

@roftone
Copy link
Author

roftone commented May 9, 2023

salesforcecli/plugin-deploy-retrieve#610 should fix this. Cheers.

Awesome, I'll test it as soon as it goes live.

@WillieRuemmele
Copy link
Member

Thanks @R0Wi for the contribution 🏆

I just merged this into plugin-deploy-retrieve which will be available in tonight's nightly build of the CLIs 🎉

@R0Wi
Copy link

R0Wi commented May 15, 2023

Just tested the current nightly (https://developer.salesforce.com/media/salesforce-cli/sfdx/versions/7.202.3/8fc437b/sfdx-v7.202.3-8fc437b-linux-x64.tar.xz) and the error seems to be gone.

@roftone
Copy link
Author

roftone commented May 19, 2023

@R0Wi
Just tested the fix, works great. Thanks.

@roftone roftone closed this as completed May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants