-
-
Notifications
You must be signed in to change notification settings - Fork 106
feat: add NUnit and MSTest migration analyzers and code fixers #3195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add base classes for shared migration logic (BaseMigrationAnalyzer, BaseMigrationCodeFixProvider) - Implement NUnitMigrationAnalyzer to detect NUnit code - Implement NUnitMigrationCodeFixProvider to convert NUnit to TUnit - Implement MSTestMigrationAnalyzer to detect MSTest code - Implement MSTestMigrationCodeFixProvider to convert MSTest to TUnit - Add comprehensive tests for both migration paths - Add diagnostic rules TUNU0001 and TUMS0001 - Share common code through base classes and helper methods Key conversions: NUnit: [Test], [TestCase], [SetUp], [TearDown], Assert.That → TUnit equivalents MSTest: [TestMethod], [DataRow], [TestInitialize], [TestCleanup], Assert.AreEqual → TUnit equivalents 🤖 Generated with Claude Code Co-Authored-By: Claude <[email protected]>
- Add comprehensive migration guide for NUnit to TUnit - Add comprehensive migration guide for MSTest to TUnit - Include automated code fixer instructions using TUNU0001 and TUMS0001 - Document manual migration steps for all attributes, assertions, and lifecycle methods - Provide side-by-side comparison examples for common patterns - Highlight key differences and async-by-default approach 🤖 Generated with Claude Code Co-Authored-By: Claude <[email protected]>
- Add 'using TUnit.Analyzers.Migrators.Base;' to NUnit and MSTest code fixers - Fixes compilation error CS0103 🤖 Generated with Claude Code Co-Authored-By: Claude <[email protected]>
- Fix MSTest false positives by changing TargetFrameworkNamespace from 'Microsoft' to 'Microsoft.VisualStudio.TestTools.UnitTesting' - Eliminate duplicate GetDeclaredSymbol calls for performance improvement - Add error handling to code fixers with try-catch blocks Co-authored-by: Tom Longhurst <[email protected]>
This was referenced Nov 6, 2025
This was referenced Nov 13, 2025
This was referenced Nov 24, 2025
This was referenced Dec 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.