run-tests

Run .NET Tests

Detect the project system, test platform, and framework, then use the repository-compatible build and test runner.

When to Use

• User wants to run tests in a .NET project
• User needs to run a subset of tests using filters
• User needs help detecting which test platform (VSTest vs MTP) or framework is in use
• User wants to understand the correct filter syntax for their setup

When Not to Use

• User needs to write or generate test code (use code-testing-agent; use writing-mstest-tests for a specifically MSTest API/pattern request)
• User needs to migrate from VSTest to MTP (use migrate-vstest-to-mtp)
• User wants to iterate on failing tests without rebuilding (use mtp-hot-reload)
• User needs CI/CD pipeline configuration (use CI-specific skills)
• User needs to debug a test (use debugging skills)

Inputs

Critical Rules — Avoid Cross-Platform Mistakes

These are the most common agent mistakes. Internalize before proceeding:

Workflow

Quick Reference

Detection files to always check (in order): global.json -> .csproj -> packages.config -> Directory.Build.props -> Directory.Packages.props -> repository scripts/CI documentation

If the prompt names a subset of tests (e.g., "integration tests", "smoke tests", a specific class, a specific TFM), plan to apply the matching filter / --framework in Step 3 — do not run the whole suite.

Step 1: Detect the test platform and framework

1. Classify SDK-style vs. classic non-SDK using platform-detection.
2. For classic projects, inspect packages.config, assembly references, scripts, CI, README*, and AGENTS.md; use their MSBuild/test-runner command. Do not migrate or add modern package references.
3. For SDK-style projects, run dotnet --version in the project directory.
4. Read global.json to determine dotnet test mode on SDK 10+.
5. Read .csproj, Directory.Build.props, and Directory.Packages.props to determine whether VSTest mode executes VSTest or bridges to MTP.

Classic non-SDK projects

The checked-in command is authoritative. A common VSTest sequence is:

MSBuild.exe MySolution.sln /t:Build /p:Configuration=Debug
vstest.console.exe path\to\MyTests.dll /Logger:trx

Filtering uses the runner's syntax, for example /TestCaseFilter:"TestCategory=Integration" with VSTest. Older repositories may use MSTest.exe or a wrapper script instead. If the required Visual Studio toolchain is unavailable, report the exact missing prerequisite and the documented command; do not claim success from dotnet test.

What to look for in each file:

Quick detection summary:

Step 2: Run tests

SDK-style VSTest (any .NET SDK version)

dotnet test [<PROJECT> | <SOLUTION> | <DIRECTORY> | <DLL> | <EXE>]

Common flags:

MTP through VSTest mode

With <TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>, dotnet test bridges to MTP but uses VSTest-style argument parsing. This applies to SDK 8/9 and SDK 10+ when global runner is VSTest or unset. MTP-specific arguments must be passed after --:

dotnet test [<PROJECT> | <SOLUTION> | <DIRECTORY> | <DLL> | <EXE>] -- <MTP_ARGUMENTS>

Native MTP mode with .NET SDK 10+

With the global.json runner set to Microsoft.Testing.Platform, dotnet test natively understands MTP arguments without --:

dotnet test
    [--project <PROJECT_OR_DIRECTORY>]
    [--solution <SOLUTION_OR_DIRECTORY>]
    [--test-modules <EXPRESSION>]
    [<MTP_ARGUMENTS>]

Examples:

# Run all tests in a project
dotnet test --project path/to/MyTests.csproj

# Run all tests in a directory containing a project
dotnet test --project path/to/

# Run all tests in a solution (sln, slnf, slnx)
dotnet test --solution path/to/MySolution.sln
dotnet test --solution path/to/MySolution.slnf
dotnet test --solution path/to/MySolution.slnx

# Run all tests in a directory containing a solution
dotnet test --solution path/to/

# Run with MTP flags
dotnet test --project path/to/MyTests.csproj --report-trx --blame-hang-timeout 5min

Note: Native MTP mode does not accept a bare positional argument like VSTest mode. Use --project, --solution, or --test-modules.

Common MTP flags

These flags apply to MTP in both modes. Pass them after -- in VSTest mode and directly in native MTP mode.

Important: dotnet test/MSBuild flags such as --framework, --no-build, --configuration, and --verbosity always go before --. Only MTP application arguments go after -- in VSTest mode. For example: dotnet test --framework net9.0 -- --report-trx.

Built-in flags (always available):

Extension-dependent flags (require the corresponding extension package to be registered):

Some frameworks (e.g., MSTest) bundle common extensions by default. Others may require explicit package references. If a flag is not recognized, check that the corresponding extension package is referenced in the project.

Alternative MTP invocations

MTP test projects are standalone executables. Beyond dotnet test, they can be run directly:

# Build and run
dotnet run --project <PROJECT_PATH>

# Run a previously built DLL
dotnet exec <PATH_TO_DLL>

# Run the executable directly (Windows)
<PATH_TO_EXE>

These alternative invocations accept MTP command line arguments directly (no -- separator needed).

Step 3: Run filtered tests

See the filter-syntax skill for the complete filter syntax for each platform and framework combination. Key points:

• VSTest (MSTest, xUnit v2, NUnit): dotnet test --filter <EXPRESSION> with =, !=, ~, !~ operators
• MTP -- MSTest and NUnit: Same --filter syntax as VSTest; pass after -- in VSTest mode and directly in native MTP mode.
• MTP -- xUnit v3: Uses --filter-class, --filter-method, --filter-trait (not VSTest expression syntax). For a single combined expression (e.g., a class-name pattern AND a trait), use --filter-query with the xUnit v3 query filter language: path segments /<assembly>/<namespace>/<class>/<method> with * wildcards and a [Trait=Value] qualifier — for example dotnet test -- --filter-query "/*/*/*IntegrationTests*/*[Category=Smoke]". See the filter-syntax skill for the full query language.
• MTP -- TUnit: Uses --treenode-filter with path-based syntax

When the user names a test category, trait, or group

When the prompt names a subset of tests by category (e.g., "integration tests", "unit tests", "smoke tests", "fast tests"), do not run all tests — translate the user's vocabulary into the platform-appropriate filter:

1. Inspect the test source files for filter-attribute annotations that match the named group:

   Framework	Attribute	Filter property
   MSTest	[TestCategory("Integration")]	TestCategory
   NUnit	[Category("Integration")]	TestCategory (mapped)
   xUnit v2	[Trait("Category", "Integration")]	Category
   xUnit v3	[Trait("Category", "Integration")]	Category (use --filter-trait)
   TUnit	[Category("Integration")]	Category

2. Build the filter expression and combine it with the platform-correct invocation. For "run the integration tests" against an MSTest project:

   Mode / platform	Framework	Command
   VSTest mode / VSTest	MSTest	dotnet test --filter "TestCategory=Integration"
   VSTest mode / MTP bridge	MSTest	dotnet test -- --filter "TestCategory=Integration"
   Native MTP mode	MSTest	dotnet test --filter "TestCategory=Integration"
   VSTest mode / MTP bridge	xUnit v3	dotnet test -- --filter-trait "Category=Integration"
   Native MTP mode	xUnit v3	dotnet test --filter-trait "Category=Integration"
   VSTest mode / MTP bridge	TUnit	dotnet test -- --treenode-filter "/*/*/*/*[Category=Integration]"
   Native MTP mode	TUnit	dotnet test --treenode-filter "/*/*/*/*[Category=Integration]"

3. If you cannot find a matching attribute, ask the user to confirm the category name or fall back to a name-pattern filter (e.g., --filter "FullyQualifiedName~Integration").

Validation

• Test platform (VSTest or MTP) was correctly identified
• Project system (SDK-style or classic non-SDK) was correctly identified
• Test framework (MSTest, xUnit, NUnit, TUnit) was correctly identified
• Correct repository-compatible runner was used; dotnet test syntax was validated only for SDK-style projects
• When the user named a test category/trait/group, the appropriate filter was applied (not "run all tests")
• Filter expressions used the syntax appropriate for the platform and framework
• Test results were clearly reported to the user

Common Pitfalls

Troubleshooting

Common error messages and how to resolve them: