ci: Use --no-progress for easier to read output in tests
#21271
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR improves the readability of CI test output by adding the --no-progress flag to the dotnet run command in the WASM automated UI tests script.
- Adds
--no-progressflag to suppress progress indicators during test execution
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-21271/docs/index.html |
|
🤖 Your WebAssembly Skia Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-21271/wasm-skia-net9/index.html |
|
|
|
@Youssef1313 what's easier about it? |
|
After: 
Before: 
The repetitive "[+0/x0/?13] SamplesApp.UITests.dll (net8.0|x64)(0s)" part makes it harder to navigate through. In a capable terminal, that line gets updated in place so it's nicer (the numbers shown are passed/failed/skipped). But on CI, it gets repeated making it harder to read. |
|
I see! Still, it's a useful information, particularly for the troubleshooting of the stalled tests. |
|
Up to you to decide then. Feel free to close if you are comfortable with current output. It's mostly my personal preference :) |
GitHub Issue: closes #
PR Type:
What is the current behavior? 🤔
What is the new behavior? 🚀
PR Checklist ✅
Please check if your PR fulfills the following requirements:
Screenshots Compare Test Runresults.Other information ℹ️