mtp-hot-reload

Configures Microsoft Testing Platform hot reload to iterate on failing tests without rebuilding.

1|Updated Jul 27, 2026
One-click install
npx skills add https://github.com/FittyAr/Cardscape --skill mtp-hot-reload-fittyar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mtp-hot-reload
Source: https://github.com/FittyAr/Cardscape/tree/main/.agents/skills/mtp-hot-reload
Command: npx skills add https://github.com/FittyAr/Cardscape --skill mtp-hot-reload-fittyar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Microsoft.Testing.Extensions.HotReload.

What problem does it solve? Fixing failing tests normally requires a full rebuild and test run for every code change, which slows down the fix-verify loop. This Skill sets up Microsoft Testing Platform (MTP) hot reload so the test host stays running and automatically re-runs affected tests whenever you edit code. ## Core Features & Use Cases - Guided Setup: Installs the Microsoft.Testing.Extensions.HotReload NuGet package and enables the TESTINGPLATFORM_HOTRELOAD_ENABLED environment variable via shell or launchSettings.json. - Framework-Aware Filtering: Provides the correct test filter syntax for MSTest, NUnit, xUnit v3, and TUnit so you iterate only on the failing tests. - Iterative Workflow: Runs the test host in console mode with dotnet run, watches for code changes, and re-executes affected tests automatically. - Use Case: You have three failing integration tests. Instead of rebuilding after each fix attempt, you enable hot reload, edit the production code, and watch the tests re-run instantly until they pass. ## Quick Start Set up MTP hot reload in my test project and run my failing tests so I can iterate on the fix without rebuilding.

Frequently Asked Questions about mtp-hot-reload

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run .NET tests without rebuilding after each code change?▼

Use Microsoft Testing Platform hot reload by installing the Microsoft.Testing.Extensions.HotReload package, setting TESTINGPLATFORM_HOTRELOAD_ENABLED=1, and running the test project with dotnet run. The test host stays active and re-runs affected tests when you edit code.

How to set up MTP hot reload in a test project?▼

Add the Microsoft.Testing.Extensions.HotReload NuGet package, then set the TESTINGPLATFORM_HOTRELOAD_ENABLED environment variable to 1 in your shell or in Properties/launchSettings.json. Run tests with dotnet run --project <path> instead of dotnet test.

Does hot reload work with VSTest or dotnet test?▼

No, hot reload requires Microsoft Testing Platform and does not work with VSTest or the dotnet test command. You must run the test project directly with dotnet run, or migrate from VSTest to MTP first.

Can I use MTP hot reload in Visual Studio Test Explorer?▼

No, MTP hot reload currently works in console mode only. Visual Studio and VS Code Test Explorer are not supported; Visual Studio has its own separate built-in Test Explorer hot reload feature.

Why does hot reload not pick up my code changes?▼

Some edits are unsupported rude edits, such as adding new types or changing method signatures, which require restarting the test host. Also verify the environment variable is set and you used dotnet run rather than dotnet test.

How do I filter which tests run with MTP hot reload?▼

Pass a filter after -- when running the project, using framework-specific syntax: --filter "FullyQualifiedName~Name" for MSTest and NUnit, --filter-method for xUnit v3, or --treenode-filter for TUnit.