Revise dotnet test behavior if test app targets `netX.0;netX.0-windows` #49924

Open

Open

Revise dotnet test behavior if test app targets netX.0;netX.0-windows#49924

Assignees

Labels

Area-dotnet test

Milestone

opened

on Jul 24, 2025

sdk/src/Cli/dotnet/Commands/Test/Terminal/TerminalTestReporter.cs

Lines 200 to 212 in 99c8904

    
           private TestProgressState GetOrAddAssemblyRun(string assembly, string? targetFramework, string? architecture, string? executionId) 
        
           { 
        
               string key = $"{assembly}|{targetFramework}|{architecture}|{executionId}"; 
        
               return _assemblies.GetOrAdd(key, _ => 
        
               { 
        
                   IStopwatch sw = CreateStopwatch(); 
        
                   var assemblyRun = new TestProgressState(Interlocked.Increment(ref _counter), assembly, targetFramework, architecture, sw); 
        
                   int slotIndex = _terminalWithProgress.AddWorker(assemblyRun); 
        
                   assemblyRun.SlotIndex = slotIndex; 
        
                   return assemblyRun; 
        
               }); 
        
           }

Both target frameworks will likely map to the same key. This can be buggy, especially with retry.

Note that targetFramework is best-effort and both netX.0 and netX.0-platform are likely going to map to netX.0 today.

Metadata

Assignees

Youssef1313

Labels

Area-dotnet test

Type

No type

Projects

No projects

Milestone

10.0.1xxNo due date

Relationships

None yet

Development

No branches or pull requests