We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add the complement to --no-ansi, that forces --ansi output, even if output is redirected.
When running the tests from a PowerShell script, I may want to display the test output but not have it as output from the PowerShell function.
mytest.exe | Out-Host if ($LASTEXITCODE){ throw "test failed" }
This removes all coloring from the output, even though it's logically equivalent to passing it directly to the terminal for display.
Add --ansi parameter that forces ansi output, regardless of redirection. Let the user decide.
--ansi
Always output ansi unless the user explicitly uses --no-ansi. That has the drawback of potentially breaking existing scripts.
--no-ansi
The text was updated successfully, but these errors were encountered:
It's probably a quick and easy update so I don't see why not! Thanks for the suggestion @powercode.
cc @mariam-abdulla as it might require some porting to dotnet test.
dotnet test
Sorry, something went wrong.
No branches or pull requests
Summary
Add the complement to --no-ansi, that forces --ansi output, even if output is redirected.
Background and Motivation
When running the tests from a PowerShell script, I may want to display the test output but not have it as output from the PowerShell function.
This removes all coloring from the output, even though it's logically equivalent to passing it directly to the terminal for display.
Proposed Feature
Add
--ansi
parameter that forces ansi output, regardless of redirection. Let the user decide.Alternative Designs
Always output ansi unless the user explicitly uses
--no-ansi
.That has the drawback of potentially breaking existing scripts.
The text was updated successfully, but these errors were encountered: