Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

VSTest -> Microsoft.Testing.Platform Migration · dotnet | DecimalAI

testingby dotnet

VSTest -> Microsoft.Testing.Platform Migration

dotnet/migrate-vstest-to-mtp

Source dotnet/skills ↗License MIT

Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP).

SkillScore70Maintained

Automatic

Coding pack

Last verified 9/9/2026

What it changes

Passed 11 of 16 test cases with the skill, and 7 of 16 without it.

Without skill43%

With skill70%

Checks it passed that the model alone missed

The response names the YTest.MTP.XUnit2 NuGet package.
The response instructs removing the UseVSTest property.
The response uses --filter-method for targeting a specific test method.

and 12 more in the full report

9 fixed7 passed either way4 still failing3 broke

Pass-rate lift: +26 pp
Tokens: +167%
Agent turns: 0%
Response time: -7%

Model gemini-3.6-flashMeasured 9/9/2026v316 of 23 cases passed with skill · 16 comparable

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/dotnet-migrate-vstest-to-mtp/SKILL.md https://app.decimal.ai/s/dotnet-migrate-vstest-to-mtp/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add dotnet-migrate-vstest-to-mtp, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/dotnet-migrate-vstest-to-mtp/ and pins it in .decimal/skills.lock

decimalai skills add dotnet-migrate-vstest-to-mtp

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/dotnet-migrate-vstest-to-mtp/SKILL.md https://app.decimal.ai/s/dotnet-migrate-vstest-to-mtp/SKILL.md

Raw file: /s/dotnet-migrate-vstest-to-mtp/SKILL.md ↗ · machine-readable summary at /s/dotnet-migrate-vstest-to-mtp.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 9

Prompt

We have an NUnit 4 unit test project targeting .NET 8. We want to enable the Microsoft.Testing.Platform runner centrally in `Directory.Build.props`. What property name enables NUnit's MTP runner, what project output type is required, and what minimum version of `NUnit3TestAdapter` must be referenced?

What was checked, without and with the skill
Checked	Without skill	With skill
The response specifies EnableNUnitRunner set to true.	Passed	Passed
The response identifies NUnit3TestAdapter version 5.0.0 or higher as the required minimum adapter package version.	Missed	Passed
The response specifies setting OutputType to Exe for the test project.	Passed	Passed

case-08 · gemini-3.6-flash · 9/9/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md404 linessingle file

VSTest -> Microsoft.Testing.Platform Migration

Migrate a .NET test solution from VSTest to Microsoft.Testing.Platform (MTP). The outcome is a solution where all test projects run on MTP, dotnet test works correctly, and CI/CD pipelines are updated.

First Action

Inspect the supplied project, Directory.Build.props, global.json, and CI files before searching the web or answering from memory. Resolve the framework and SDK mode first: .NET 9 and earlier use the compatibility property plus the -- separator; .NET 10 native MTP uses global.json, removes that property, and passes MTP arguments without the separator. For central properties, never condition on IsTestProject in Directory.Build.props; use a property already available there, such as MSBuildProjectName.

Important: Do not mix VSTest-based and MTP-based .NET test projects in the same solution or run configuration -- this is an unsupported scenario.

When to Use

Switching from VSTest to Microsoft.Testing.Platform for any supported test framework
Enabling dotnet run / dotnet watch / direct executable execution for test projects
Enabling Native AOT or trimmed test execution
Replacing vstest.console.exe with dotnet test on MTP
Updating CI/CD pipelines from the VSTest task to the .NET Core CLI task
Updating dotnet test arguments from VSTest syntax to MTP syntax

When Not to Use

The project already runs on Microsoft.Testing.Platform and there is no remaining MTP behavioral difference to resolve (e.g., exit code 8 for zero tests discovered)
Migrating between test frameworks (e.g., MSTest to xUnit.net) -- different effort entirely
The project builds UWP or packaged WinUI test projects -- MTP does not support these yet
The solution mixes .NET and non-.NET test adapters (e.g., JavaScript or C++ adapters) -- VSTest is required
Upgrading MSTest versions -- use migrate-mstest-v1v2-to-v3 or migrate-mstest-v3-to-v4

Inputs

Input	Required	Description
Project or solution path	No	The `.csproj`, `.sln`, or `.slnx` entry point containing test projects. Discover it yourself by globbing the working directory; ask only when nothing is found or the choice is genuinely ambiguous
Test framework	No	MSTest, NUnit, xUnit.net v2, or xUnit.net v3. Auto-detected from package references
.NET SDK version	No	Determines `dotnet test` integration mode. Prefer the repository's `global.json` or explicitly stated CI SDK; use host `dotnet --version` only when the repository does not pin or state one

Track record

Benchmark

11 / 16

test cases passed, vs 7 / 16 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v5 — 9/8/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

dotnet / skills

plugins/dotnet-test-migration/skills/migrate-vstest-to-mtp/SKILL.md

View on GitHub ↗

License MITImported 9/8/2026Version v3

Other skills for the same job

Published skills whose descriptions closely match this one, with their headline benchmark lift.

managedcode/migrate-vstest-to-mtpMigrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizingClose match+41 pp pass-rate lift

More skills from the same source and nearby in the registry, with their headline benchmark lift.

Ready to supercharge your AI agents?

See it in action

What's inside

VSTest -> Microsoft.Testing.Platform Migration

First Action

When to Use

When Not to Use

Inputs

Track record

Benchmark

Adoption

SkillSafety

Source

Other skills for the same job

Related skills