The CurrentTestApplicationModuleInfo.GetCurrentExecutableInfo() method was always using Environment.GetCommandLineArgs() to retrieve command line arguments, ignoring any custom arguments passed to TestApplication.CreateBuilderAsync(). This caused issues with extensions like retry that depend on seeing the actual arguments used to configure the test application.

Problem

When users write custom code to modify arguments before calling CreateBuilderAsync():

// User's custom Main method
if (args.Length == 0)
{
    args = ["--retry-failed-tests", "1"];
}

var builder = await TestApplication.CreateBuilderAsync(args);
using var app = await builder.BuildAsync();
return await app.RunAsync();

The retry extension would fail because GetCurrentExecutableInfo() returned the original empty command line arguments from Environment.GetCommandLineArgs(), not the modified args ["--retry-failed-tests", "1"] passed to CreateBuilderAsync().

Solution

This PR implements a service-based approach to capture and provide access to the original arguments passed to CreateBuilderAsync():

1. Created ICommandLineArgumentsProvider interface and implementation to store the original arguments
2. Modified the builder chain to pass arguments through TestApplication → TestApplicationBuilder → TestHostBuilder
3. Updated GetCurrentExecutableInfo() to intelligently combine custom arguments with environment arguments
4. Maintained backward compatibility by falling back to environment arguments when no custom arguments are provided

Key Features

Smart Argument Handling: The implementation correctly handles different execution scenarios:

• Executable scenarios: Uses custom args while preserving executable name from environment
• Dotnet scenarios: Combines assembly path from environment with custom args to ensure proper command reconstruction
• Backward compatibility: Falls back to original behavior when no custom args are provided

Example transformations:

// Dotnet with custom args:
// Environment: ["dotnet", "MyTest.dll"] 
// Custom: ["--retry-failed-tests", "1"]
// Result: ["exec", "dotnet", "MyTest.dll", "--retry-failed-tests", "1"]

Testing

Added comprehensive unit tests covering:

• Executable scenarios with custom arguments
• Dotnet scenarios with custom arguments
• Backward compatibility when no custom arguments are provided

The fix ensures that retry and other extensions now correctly see and use the arguments that were actually passed to CreateBuilderAsync(), while maintaining full compatibility with dotnet execution scenarios.

Fixes #5239.

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.