migrate-mstest-v1v2-to-v3

F-U-S-E-E/FuseDevelopmentGroup

SkillLoads cleanly

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…

Scores
out of 100 · grade B+

2026-08-18

Works

40% of the score

100/100

Loads cleanly: valid frontmatter, required fields present, no dangling references.

Maintained

25% of the score

100/100

no commits in the last 12 weeks

Adopted

20% of the score

13/100

8 stars on the source repo.

Documented

15% of the score

81/100

1,462 words with worked examples.

Loads cleanly. Every structural check Claude Code needs to register this passed. Last commit today.

Install

npx skills add F-U-S-E-E/FuseDevelopmentGroup/migrate-mstest-v1v2-to-v3

What it says 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 FOR: upgrading from MSTest v1 assembly references (Microsoft.VisualStudio.QualityTools.UnitTestFramework) or MSTest v2 NuGet (MSTest.TestFramework 1.x-2.x) to MSTest v3, fixing assertion overload errors (AreEqual/AreNotEqual), updating DataRow constructors, replacing .testsettings with .runsettings, timeout behavior changes, target framework compatibility (.NET 5 dropped -- use .NET 6+; .NET Fx older than 4.6.2 dropped), adopting MSTest.Sdk. First step toward MSTest v4 -- after this, use migrate-mstest-v3-to-v4. DO NOT USE FOR: migrating to MSTest v4 (use migrate-mstest-v3-to-v4), migrating between frameworks (MSTest to xUnit/NUnit), or general .NET upgrades unrelated to MSTest.

Every number above came out of reading the file and its repository. Nothing is a judgement call, nothing is a model’s opinion, and nothing can be paid for. The full method is published. Source last committed 2026-08-18.

Also in F-U-S-E-E/FuseDevelopmentGroup

Other artifacts published from the same repository.
Artifact	What the check found	Type	Reach	Last commit
analyzing-dotnet-performanceF-U-S-E-E/FuseDevelopmentGroup	clean	Skill	8 stars	today
apple-crash-symbolicationF-U-S-E-E/FuseDevelopmentGroup	clean	Skill	8 stars	today
clr-activation-debuggingF-U-S-E-E/FuseDevelopmentGroup	clean	Skill	8 stars	today
coverage-analysisF-U-S-E-E/FuseDevelopmentGroup	clean	Skill	8 stars	today
directory-build-organizationF-U-S-E-E/FuseDevelopmentGroup	clean	Skill	8 stars	today
dotnet-aot-compatF-U-S-E-E/FuseDevelopmentGroup	clean	Skill	8 stars	today

Other testing & qa skills

Browse all

Same category, same type, ranked by score.
Artifact	What the check found	Category	Reach	Last commit
skill-creatoranthropics/skills	No license	Testing & QA	358,827 installs	today
systematic-debuggingobra/superpowers	clean	Testing & QA	232,863 installs	2 days ago
webapp-testinganthropics/skills	No license	Testing & QA	138,299 installs	today
test-driven-developmentobra/superpowers	clean	Testing & QA	204,536 installs	2 days ago
migrate-to-shoehornmattpocock/skills	clean	Testing & QA	238,622 installs	today
playwright-component-testingmicrosoft/playwright	clean	Testing & QA	95k stars	today

Put this measurement in your README

A badge carrying how many listings this index holds from the repository and how many pass every static structural check. It reads from this index every time somebody loads your page, so it changes when the measurement changes and there is nothing to keep up to date. Free, no account, and the value is not something you or we can set by hand.

[![SkillWorks](https://toolproof.kynth.studio/badge/skillworks/F-U-S-E-E/FuseDevelopmentGroup.svg)](https://skillworks.kynth.studio/?q=F-U-S-E-E%2FFuseDevelopmentGroup)

Would rather not hotlink us? Every badge is also served in shields.io’s endpoint schema, so shields renders the image and your readers never talk to our domain:

Published by Toolproof, the masthead over this index and eight others. The method behind the number is at toolproof.kynth.studio/methodology, and the whole thing is readable as JSON with no key at /api.