-
Notifications
You must be signed in to change notification settings - Fork 724
[CI] Test summary reporter improvements #9263
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR improves the test summary reporter by adding log artifact links, addressing Windows run issues, and increasing logging detail.
- Adds log artifact links in report headers
- Fixes Windows execution paths and logging
- Enhances error messaging and stdout logging for missing or empty test files
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| tools/GenerateTestSummary/TestSummaryGenerator.cs | Refactors report generation to include optional URL links and additional logging output for test failures |
| tools/GenerateTestSummary/Program.cs | Updates handling of input parameters and error messages; enforces combined summary option constraints |
| .github/workflows/run-tests.yml | Replaces shell command with PowerShell script ensuring Windows compatibility and proper command invocation |
Comments suppressed due to low confidence (1)
.github/workflows/run-tests.yml:306
- Consider verifying that the DOTNET_SCRIPT environment variable is defined and valid to avoid potential runtime issues on systems where the variable might not be set.
& ${{ env.DOTNET_SCRIPT }} run --project "${{ github.workspace }}/tools/GenerateTestSummary/GenerateTestSummary.csproj" -- "${{ github.workspace }}/testresults" -u "${{ steps.upload-logs.outputs.artifact-url }}"
Co-authored-by: Dan Moseley <danmose@microsoft.com>
RussKie
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with comments
| : "os?"; | ||
| : throw new InvalidOperationException($"Could not determine OS from file path: {filePath}"); | ||
|
|
||
| tableBuilder.AppendLine(CultureInfo.InvariantCulture, $"| {(failed > 0 ? "❌" : "✅")} [{os}] {GetTestTitle(filePath)} | {passed} | {failed} | {skipped} | {total} |"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed in my tests that even when there are not test results (i.e., all 0, can happen when the runner crashed) we show the "tick". It looks odd.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you share an example of that, so I can fix accordingly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ig-raiderler anything you'd do differently? we welcome improvements |

Uh oh!
There was an error while loading. Please reload this page.