mtp-hot-reload

Configures Microsoft Testing Platform hot reload to iterate test fixes without rebuilding.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/Netcodr81/kinetic-reports --skill mtp-hot-reload-netcodr81
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mtp-hot-reload
Source: https://github.com/Netcodr81/kinetic-reports/tree/main/.github/skills/mtp-hot-reload
Command: npx skills add https://github.com/Netcodr81/kinetic-reports --skill mtp-hot-reload-netcodr81

SYSTEM DOCUMENTATION & REQUIREMENTS

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 when you edit code. ## Core Features & Use Cases - Platform Detection: Verifies the project uses Microsoft Testing Platform rather than VSTest, since hot reload only works with MTP. - Guided Setup: Walks through installing the Microsoft.Testing.Extensions.HotReload NuGet package and enabling the TESTINGPLATFORM_HOTRELOAD_ENABLED environment variable via shell or launchSettings.json. - Iterative Workflow: Runs tests with dotnet run in console mode, applies framework-specific filters (MSTest, NUnit, xUnit v3, TUnit), and re-runs tests automatically on code changes. - Use Case: You have three failing xUnit tests. After setup, you start the test host once, edit the production code, and watch the tests re-run instantly after each save until they pass. ## Quick Start Set up MTP hot reload in my test project so I can iterate on my failing tests without rebuilding between changes.

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: install the Microsoft.Testing.Extensions.HotReload package, set TESTINGPLATFORM_HOTRELOAD_ENABLED=1, and run tests with dotnet run --project <path>. The test host stays running 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, either in your shell or in Properties/launchSettings.json. Run the project directly with dotnet run instead of dotnet test.

Does hot reload work with VSTest or dotnet test?▼

No. Hot reload requires Microsoft Testing Platform and console mode via dotnet run --project <path>. It does not work with VSTest, dotnet test, or Test Explorer in Visual Studio or VS Code.

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

Pass the filter after -- when running the project. MSTest and NUnit use --filter "FullyQualifiedName~TestName", xUnit v3 uses --filter-method "*TestName", and TUnit uses --treenode-filter "/*/*/ClassName/TestName".

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, and require restarting the test host. Also confirm the environment variable is set and you used dotnet run, not dotnet test.