8000 Update test result processing to use NUnitXml format and enhance logging for better clarity by TravisEz13 · Pull Request #25288 · PowerShell/PowerShell · GitHub
[go: up one dir, main page]

Skip to content

Update test result processing to use NUnitXml format and enhance logging for better clarity #25288

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

Merged
merged 3 commits into from
Apr 7, 2025

Conversation

TravisEz13
Copy link
Member
@TravisEz13 TravisEz13 commented Apr 7, 2025

PR Summary

This pull request includes several changes to improve the logging and error reporting in the test workflows, as well as to update the test result formats. The most important changes include updating the test result format from JUnitXml to NUnitXml, refactoring the process to summarize Pester test results, and enhancing the logging in various scripts.

Test result format updates:

  • Updated the output format from JUnitXml to NUnitXml in .github/actions/test/nix/action.yml and .github/actions/test/windows/action.yml. [1] [2]

Refactoring Pester test results processing:

  • Removed inline script for summarizing Pester test results and replaced it with a call to process-pester-results.ps1 in .github/actions/test/process-pester-results/action.yml.
  • Added a new script process-pester-results.ps1 to handle the summarization of Pester test results, including more detailed metrics.

Enhancing logging:

Formatting improvements:

  • Improved the formatting of error messages in Show-PSPesterError and Test-XUnitTestResults functions in build.psm1 for better readability. [1] [2]

PR Context

JUnit Test results would often fail to serialize at all or properly. Switching back to NUnit because the format was reliable.

PR Checklist

8000
Copy link
Contributor
@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 3 out of 5 changed files in this pull request and generated 1 comment.

Files not reviewed (2)
  • .github/actions/test/process-pester-results/process-pester-results.ps1: Language not supported
  • build.psm1: Language not supported

@TravisEz13 TravisEz13 added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Apr 7, 2025
@TravisEz13 TravisEz13 marked this pull request as ready for review April 7, 2025 19:11
@TravisEz13
Copy link
Member Author

/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI

@TravisEz13 TravisEz13 enabled auto-merge (squash) April 7, 2025 19:24
Copy link
Azure Pipelines successfully started running 2 pipeline(s).

@TravisEz13 TravisEz13 merged commit 71e9532 into master Apr 7, 2025
42 checks passed
@TravisEz13 TravisEz13 deleted the workflow-logging-enhancements branch April 7, 2025 21:03
pwshBot pushed a commit to pwshBot/PowerShell that referenced this pull request Apr 11, 2025
@TravisEz13
Copy link
Member Author

@PowerShell/powershell-maintainers triage decision - required infrastructure change

Sysoiev-Yurii pushed a commit to Sysoiev-Yurii/PowerShell that referenced this pull request May 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backport-7.4.x-Migrated Backport-7.5.x-Migrated CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0