[Feature]: Environment variable support for --disable-logo and --no-progress flags

[timwkosatec]

Problem Statement

Current behavior: The --disable-logo and --no-progress flags must be passed on every command-line invocation
when running the test executable directly. There's no way to set these as defaults via environment variables.

Desired behavior: Environment variables like TUNIT_DISABLE_LOGO=true and TUNIT_NO_PROGRESS=true that apply
these flags automatically, following the existing pattern of TUNIT_GITHUB_REPORTER_STYLE and
TUNIT_DISABLE_GITHUB_REPORTER.

Proposed Solution

Add environment variable support:

• TUNIT_DISABLE_LOGO=true → equivalent to --disable-logo
• TUNIT_NO_PROGRESS=true → equivalent to --no-progress

Alternatives Considered

• TestingPlatformCommandLineArguments MSBuild property - only works with dotnet test, not direct .exe execution
• Shell aliases - not portable across environments

Feature Category

Test Execution / Lifecycle

How important is this feature to you?

Nice to have - would improve my experience

Additional Context

Why This Benefits Most Users

1. AI/LLM coding assistants (Claude Code, Copilot, Cursor) run tests and parse output - the ASCII banner wastes
   tokens and adds noise
2. CI/CD pipelines can set env vars globally instead of modifying every test command
3. Consistency with existing TUnit env var patterns (TUNIT_*)

Additional Context

Similar pattern exists in other tools (e.g., DOTNET_NOLOGO, NO_COLOR).

Contribution

• I'm willing to submit a pull request for this feature

[thomhurst]

TUNIT_NO_PROGRESS - The --no-progress flag is a built-in Microsoft Testing Platform feature, not a TUnit-specific flag. TUnit doesn't have control over this behavior as it's handled entirely by the platform before TUnit is initialized.

Possible workaround

1. MSBuild Property (works with dotnet test):

   <PropertyGroup>
     <TestingPlatformCommandLineArguments>--no-progress</TestingPlatformCommandLineArguments>
   </PropertyGroup>

For full --no-progress environment variable support, a feature request would need to be filed with the Microsoft Testing Platform team.

[timwkosatec]

Wow, that was fast, thanks! I'll test it once released.
This will be really helpful for avoiding context limits with my LLM's when running lots of tests during development.