-
Notifications
You must be signed in to change notification settings - Fork 77
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
Comments
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. |
This issue has been linked to a new work item: W-13048665 |
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? |
Yes, sfdx-cli 7.196.8 (core) The command is: 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. |
great, and does it work correctly if you use |
^ more of a bug, but the WI has already been created |
Yes, that's the command that we are using again. |
salesforcecli/plugin-deploy-retrieve#610 should fix this. Cheers. |
Awesome, I'll test it as soon as it goes live. |
Thanks @R0Wi for the contribution 🏆 I just merged this into |
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. |
@R0Wi |
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](https://user-images.githubusercontent.com/131013134/232555992-2a848edb-bcb3-43ae-9b14-0a78ce31bc18.png)
After:
![image](https://user-images.githubusercontent.com/131013134/232556276-72fe8074-dbfd-402c-80d1-747ac112c261.png)
The text was updated successfully, but these errors were encountered: