Skip to content

Test terminal logger with file-based apps #50187

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 1 commit into from
Aug 13, 2025

Conversation

jjonescz
Copy link
Member

@jjonescz jjonescz commented Aug 12, 2025

To avoid regressions like the one fixed in #49969.

@jjonescz jjonescz added the Area-run-file Items related to the "dotnet run <file>" effort label Aug 12, 2025
@jjonescz jjonescz marked this pull request as ready for review August 12, 2025 15:13
@jjonescz jjonescz requested review from Copilot and a team August 12, 2025 15:13
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.

Pull Request Overview

This PR adds test coverage for the terminal logger functionality when running file-based applications to prevent regressions similar to the one fixed in a previous PR. The test ensures that the terminal logger can be properly enabled and disabled through the MSBUILDTERMINALLOGGER environment variable.

  • Adds a new parameterized test method TerminalLogger that verifies terminal logger behavior with file-based C# apps
  • Tests both enabled and disabled states of the terminal logger using combinatorial data
  • Validates the presence or absence of ANSI escape sequences in output based on the logger setting

@jjonescz jjonescz merged commit 5da79c0 into dotnet:main Aug 13, 2025
30 checks passed
@jjonescz jjonescz deleted the sprint-tl-tests branch August 13, 2025 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-run-file Items related to the "dotnet run <file>" effort
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants