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 · managedcode | DecimalAI

testingby managedcode

VSTest -> Microsoft.Testing.Platform Migration

managedcode/migrate-vstest-to-mtp

Source managedcode/dotnet-skills ↗License MIT

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

SkillScore100Maintained

Automatic

QA & Test Engineering pack

Last verified 8/19/2026

What it changes

Passed 22 of 22 test cases with the skill, and 13 of 22 without it.

Without skill59%

With skill100%

Checks it passed that the model alone missed

Replaces VSTest@3 task with DotNetCoreCLI@2 task
Sets command input of DotNetCoreCLI@2 task to test
Adds package reference YTest.MTP.XUnit2 to xUnit v2 projects

and 7 more in the full report

9 fixed13 passed either way0 still failing0 broke

Pass-rate lift: +41 pp
Tokens: +160%
Agent turns: 0%
Response time: -44%

Model gemini-3.6-flashMeasured 8/19/2026v122 of 22 cases passed with skill

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/managedcode-migrate-vstest-to-mtp/SKILL.md https://app.decimal.ai/s/managedcode-migrate-vstest-to-mtp/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add managedcode-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/managedcode-migrate-vstest-to-mtp/ and pins it in .decimal/skills.lock

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

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

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

Raw file: /s/managedcode-migrate-vstest-to-mtp/SKILL.md ↗ · machine-readable summary at /s/managedcode-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

Our repository runs on .NET 10 SDK and we want all `dotnet test` invocations to use native Microsoft.Testing.Platform without needing custom CLI arguments or MSBuild properties in every project. What configuration should we put in global.json?

What was checked, without and with the skill
Checked	Without skill	With skill
Configures top-level test runner property to Microsoft.Testing.Platform in global.json	Missed	Passed

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

What's inside

The instructions your model reads when the skill loads.

SKILL.md370 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.

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	Yes	The `.csproj`, `.sln`, or `.slnx` entry point containing test projects
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. Auto-detected via `dotnet --version`
CI/CD pipeline files	No	Paths to pipeline definitions that invoke `vstest.console` or `dotnet test`

Workflow

Step 1: Assess the solution

Identify the test framework for each test project -- see the platform-detection skill for the package-to-framework mapping. Key indicators:
- MSTest: References MSTest or MSTest.TestAdapter, or uses MSTest.Sdk (with <IsTestApplication> not set to false). Note: MSTest.TestFramework alone is a library dependency, not a test project.
- NUnit: References NUnit3TestAdapter
- xUnit.net: References xunit and xunit.runner.visualstudio

Track record

Benchmark

22 / 22

test cases passed, vs 13 / 22 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 v4 — 8/3/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

managedcode / dotnet-skills

catalog/Platform/Official-DotNet-Test-Migration/skills/migrate-vstest-to-mtp/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

Other skills for the same job

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

dotnet/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+26 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

When to Use

When Not to Use

Inputs

Workflow

Step 1: Assess the solution

Track record

Benchmark

Adoption

SkillSafety

Source

Other skills for the same job

Related skills