mtp-hot-reload

Enables Microsoft Testing Platform hot reload for faster iterative debugging of failing tests.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/1k-off/umbraco-observability-playground --skill mtp-hot-reload-1k-off
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mtp-hot-reload
Source: https://github.com/1k-off/umbraco-observability-playground/tree/main/.agents/skills/mtp-hot-reload
Command: npx skills add https://github.com/1k-off/umbraco-observability-playground --skill mtp-hot-reload-1k-off

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Microsoft.Testing.Extensions.HotReload, Microsoft.Testing.Platform.MSBuild.

What problem does it solve?

It solves the slow feedback loop of rebuilding between test-fix iterations when tests are failing, by enabling hot reload for Microsoft Testing Platform (MTP) test runs.

Core Features & Use Cases

  • Rapid iteration on failing tests: Re-run affected tests automatically after code changes in the test host, without the full rebuild cycle.
  • MTP-specific workflow: Works with MTP-based runners (not VSTest), helping you keep the test loop tight while staying compatible with the correct platform.
  • Repeatable developer setup: Supports enabling hot reload via environment variables or launchSettings.json for consistent local workflows.

Use case example: You have a failing integration test in an ASP.NET Core solution and need to repeatedly adjust production code and assertions until the test passes, while avoiding the cost of rebuilding every attempt.

Quick Start

Enable MTP hot reload by installing Microsoft.Testing.Extensions.HotReload, setting TESTINGPLATFORM_HOTRELOAD_ENABLED=1 (e.g., in launchSettings.json), and starting the test host with dotnet run --project <test-project-path> so it stays running and re-runs targeted tests as you edit.

Frequently Asked Questions about mtp-hot-reload

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

FAQPage Schema
How do I speed up iterative fixes for failing tests in dotnet without rebuilding every time?

Hot reload for Microsoft Testing Platform (MTP) test runs speeds up iterative fixes by re-executing affected tests after code changes without the full rebuild cycle. You apply code edits and the running test host re-runs targeted tests automatically.

How do I enable hot reload for Microsoft Testing Platform test runs?

To enable hot reload for Microsoft Testing Platform, install the Microsoft.Testing.Extensions.HotReload package, set the TESTINGPLATFORM_HOTRELOAD_ENABLED environment variable to 1, and start tests using dotnet run --project <test-project-path> instead of dotnet test.

Does MTP hot reload work with dotnet test or VSTest runners?

MTP hot reload does not work with dotnet test or VSTest runners. It requires running the test host via dotnet run so the process stays active and can apply hot reload updates to the Microsoft Testing Platform without restarting.

Can I configure MTP hot reload settings in launchSettings.json for consistent local workflows?

Yes, you can configure MTP hot reload in launchSettings.json by setting the TESTINGPLATFORM_HOTRELOAD_ENABLED environment variable to 1. This provides a repeatable developer setup for enabling hot reload across local test iterations.

When should I use hot reload for testing instead of standard test execution?

Use hot reload for testing when you have failing integration tests requiring repeated adjustments to production code and assertions. It avoids the cost of rebuilding between each attempt, keeping the feedback loop tight for local development workflows.

What is the difference between running tests with dotnet run and dotnet test for hot reload?

Running tests with dotnet run keeps the test host process active so hot reload can apply code edits and re-run tests without restarting. Using dotnet test rebuilds and restarts the process each time, preventing the hot reload mechanism from working.