Skip to content

Clarify xUnit migration docs #4798

Closed

Description

@ascott18

Problem Statement

Step 3 of the xUnit migration docs states "You should see TUXU0001 warnings in your build output for xUnit code that can be converted.". But TUXU0001 is information level and won't be in the output of dotnet build, so this step leads to confusion that the analyzer isn't working, even though it is working.

Proposed Solution

Remove this step and skip straight to applying changes, or explain that the analyzer outputs can be viewed without being applied with dotnet format analyzers --severity info --diagnostics TUXU0001 --verify-no-changes

Alternatives Considered

No response

Feature Category

Documentation

How important is this feature to you?

Nice to have - would improve my experience

Additional Context

No response

Contribution

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

Activity

  1. thomhurst commented on Feb 14, 2026

    @thomhurst
    Owner

    Thanks for the feedback.

    Did the migrators work well for you out of interest?

  2. ascott18 commented on Feb 14, 2026

    @ascott18
    ContributorAuthor

    Yes, they took care of the bulk of the work. There was some edge cases that produced unexpected results - I'll log separate issues for those. Thank you for building out the migration tooling, it made things much simpler!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions