migrate-mstest-v1v2-to-v3 Skill
Migrate MSTest v1 or v2 test project to MSTest v3. Use when user says "upgrade MSTest", "upgrade to MSTest v3", "migrate to MSTest v3", "update test framework", "modernize tests", "MSTest v3 migration", "MSTest compatibility", "MSTest v2 to v3", or build errors after updating MSTest packages from 1.x/2.x to 3.x. USE FO Published by microsoft in testfx.
Decision snapshot
Is this a fit?
Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is migrate-mstest-v1v2-to-v3 Skill?
Migrate MSTest v1 or v2 test project to MSTest v3. Use when user says "upgrade MSTest", "upgrade to MSTest v3", "migrate to MSTest v3", "update test framework", "modernize tests", "MSTest v3 migration", "MSTest compatibility", "MSTest v2 to v3", or build errors after updating MSTest packages from 1.x/2.x to 3.x. USE FO Published by microsoft in testfx. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Declared skill metadata
- Declared license: MIT
- Source file: .agents/skills/migrate-mstest-v1v2-to-v3/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use migrate-mstest-v1v2-to-v3 Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/testfx
- Skill file: .agents/skills/migrate-mstest-v1v2-to-v3/SKILL.md
What it does
Migrate MSTest v1 or v2 test project to MSTest v3. Use when user says "upgrade MSTest", "upgrade to MSTest v3", "migrate to MSTest v3", "update test framework", "modernize tests", "MSTest v3 migration", "MSTest compatibility", "MSTest v2 to v3", or build errors after updating MSTest packages from 1.x/2.x to 3.x. USE FO
Skill instructions
MSTest v1/v2 - v3 Migration Migrate a test project from MSTest v1 (assembly references) or MSTest v2 (NuGet 1.x-2.x) to MSTest v3. MSTest v3 is not binary compatible with v1/v2 -- libraries compiled against v1/v2 must be recompiled. When to Use - Project references Microsoft.VisualStudio.QualityTools.UnitTestFramework.dll (MSTest v1) - Project uses MSTest.TestFramework / MSTest.TestAdapter NuGet 1.x or 2.x - Resolving build errors after updating MSTest packages from v1/v2 to v3 - Replacing .testsettings with .runsettings - Adopting MSTest.Sdk or in-assembly parallel execution When Not to Use - Project already on MSTest v3 with no migration-related build errors (fully migrated) - Upgrading v3 to v4 -- use migrate-mstest-v3-to-v4 - Migrating between frameworks (MSTest to xUnit/NUnit) Inputs | Input | Required | Description | |-------|----------|-------------| | Project or solution path | Yes | The .csproj, .sln, or .slnx entry point containing MSTest test projects | | Build command | No
Verified compatibility and discovery
Frequently asked questions
What is migrate-mstest-v1v2-to-v3?
migrate-mstest-v1v2-to-v3 is a open-source AI agent skill with Copy skill directory. Migrate MSTest v1 or v2 test project to MSTest v3. Use when user says "upgrade MSTest", "upgrade to MSTest v3", "migrate to MSTest v3", "update test framework", "modernize tests", "MSTest v3.
Who is migrate-mstest-v1v2-to-v3 best for?
migrate-mstest-v1v2-to-v3 is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install migrate-mstest-v1v2-to-v3?
Install or run migrate-mstest-v1v2-to-v3 using Copy skill directory. Check migrate-mstest-v1v2-to-v3 for the latest setup command.
Is migrate-mstest-v1v2-to-v3 actively maintained?
migrate-mstest-v1v2-to-v3 may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.