dotnet-mstest

To configure MSTest runner models, you must first detect whether the repository uses MSTest.Sdk, UseVSTest, or the MSTest meta-package. This detection determines the correct runner configuration and ensures test execution aligns with the project's existing conventions.

Generating reproducible MSTest workflows involves reading the repository's AGENTS.md file to extract actual test commands and constraints. This allows you to produce actionable steps, code deltas, and validation artifacts tailored to the specific testing platform setup.

Yes, you can use MSTest.Sdk to plan and repair unit tests across repositories. By identifying the specific MSTest variant in use, you can generate safe, deterministic guidance and artifacts for code, documentation, configuration, and CI pipelines.

AGENTS.md documents test commands by defining the specific execution constraints and targets for the dotnet testing platform. Reading this file allows you to extract the actual test commands and propose reproducible workflows that respect project context.

MSTest unit tests may fail when switching models due to misconfigured runner settings. You must identify the correct MSTest model and apply the appropriate configuration tweaks, code changes, and test updates to ensure compatibility with the new testing platform.

Yes, Microsoft.Testing.Platform supports automated test repair by enabling the generation of concrete deliverables. You can produce code changes, configuration tweaks, and CI guidance to advance MSTest maintenance while preserving repository context.