test: add xUnit migration tests for Assert.Empty and using directive removal #4430
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add test coverage proving that the xUnit code fixer correctly handles reported issues:
Assert.Empty(List<T>)->await Assert.That(list).IsEmpty()Assert.NotEmpty(List<T>)->await Assert.That(list).IsNotEmpty()Assert.Empty(Array)->await Assert.That(array).IsEmpty()using Xunit;andusing Xunit.Abstractions;)Investigation Findings
These tests verify that the following reported issues already work correctly:
Assert.Emptyfor collectionsIsEmpty()exists onCollectionAssertionBaseusing Xunit;not removedMigrationHelpers.RemoveFrameworkUsings()handles itAssert.Throwsloses exceptionBatchFixeris configured correctlyThe issues appear to be either from older versions of TUnit or IDE-specific behavior.
Test Plan
🤖 Generated with Claude Code