TUXU0001: XUnitMigrationCodeFixProvider Fix All action not working

[thomhurst]

Description

When running the xUnit to TUnit migration code fixer using dotnet format analyzers, the Fix All action fails with the message:

Unable to fix TUXU0001. Code fix XUnitMigrationCodeFixProvider didn't return a Fix All action.

This prevents automated batch migration of test files.

Steps to Reproduce

1. Create a test project with xUnit tests
2. Add TUnit package (version 1.11.*)
3. Add the following to the csproj:

<TUnitImplicitUsings>false</TUnitImplicitUsings>
<TUnitAssertionsImplicitUsings>false</TUnitAssertionsImplicitUsings>

4. Run: dotnet format analyzers --severity info --diagnostics TUXU0001

Expected Behavior

The code fixer should convert all xUnit tests to TUnit format in batch mode.

Actual Behavior

The fixer reports "Unable to fix TUXU0001. Code fix XUnitMigrationCodeFixProvider didn't return a Fix All action" and only partially converts files.

In my test case with ~85 test files:

• Only ~54 files (~63%) were converted to use [Test] attribute
• ~31 files (~37%) were not converted at all and still have [Fact] attribute

Environment

• TUnit Version: 1.11.*
• .NET SDK: 10.0.102
• OS: Windows

Additional Context

The migration documentation at https://tunit.dev/docs/migration/xunit recommends using dotnet format analyzers for batch migration, but this approach doesn't work due to the Fix All action not being implemented.

Suggested Fix

The XUnitMigrationCodeFixProvider needs to implement the GetFixAllProvider() method to return a proper FixAllProvider that can handle batch operations.

Tests Needed

Please add tests to verify:

1. Fix All in Document scope works
2. Fix All in Project scope works
3. Fix All in Solution scope works

[claude]

Issue Analysis

Type: Bug Report
Priority: High
Root Cause: Missing GetFixAllProvider() implementation in XUnitMigrationCodeFixProvider

Summary

The xUnit migration code fixer doesn't support Fix All operations because it doesn't override GetFixAllProvider(). This prevents the recommended dotnet format analyzers workflow from working in batch mode.

Relationship to #4389

This issue is related to #4389 (closed yesterday) which reported similar symptoms of inconsistent migration. However, this issue identifies the specific technical cause: the missing Fix All provider.

Implementing GetFixAllProvider() should enable:

• Document-level batch fixes
• Project-level batch fixes
• Solution-level batch fixes

Technical Solution

The code fixer should override GetFixAllProvider() to return an appropriate FixAllProvider:

public sealed override FixAllProvider GetFixAllProvider()
{
    return WellKnownFixAllProviders.BatchFixer;
}

This will allow Roslyn to batch the fixes across multiple files when using dotnet format.

Priority Justification

• Blocks the officially documented migration workflow
• Affects large-scale migrations (63% success rate reported)
• Standard Roslyn feature expected by users
• Relatively straightforward to implement

[thomhurst]

Investigation Findings

I investigated this issue and found that Fix All is properly configured in the code fixer.

Evidence

In BaseMigrationCodeFixProvider.cs, the Fix All provider is properly implemented:

public sealed override FixAllProvider GetFixAllProvider() => WellKnownFixAllProviders.BatchFixer;

This enables the "Fix All in Document", "Fix All in Project", and "Fix All in Solution" options.

Possible Causes

If Fix All is not appearing or not working:

1. IDE-specific behavior - Some IDEs may not show Fix All options until you've applied a single fix first
2. Analyzer not loaded - The analyzer package might not be properly loaded in your IDE
3. Version mismatch - Ensure you're using the latest version of TUnit.Analyzers

Troubleshooting Steps

1. Try restarting your IDE
2. Rebuild the solution
3. Check that the TUnit.Analyzers package is properly referenced
4. Try using the command line: dotnet format analyzers --diagnostics TUXU0001

Could you provide:

1. Your IDE and version
2. TUnit version you're using
3. Does the single-file fix work correctly?
4. Screenshots of what you see when trying to use Fix All