dotnet-test

Execute selective .NET tests via dotnet test with filtering.

1|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-orchestration --skill dotnet-test-kevintsengtw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-test
Source: https://github.com/kevintsengtw/dotnet-testing-agent-orchestration/tree/main/.github/skills/dotnet-test
Command: npx skills add https://github.com/kevintsengtw/dotnet-testing-agent-orchestration --skill dotnet-test-kevintsengtw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of running .NET tests, allowing developers to quickly execute specific tests or test suites without rebuilding the entire solution, thereby accelerating the development feedback loop.

Core Features & Use Cases

  • Selective Test Execution: Run tests based on method name, class name, or specific parameter values for xUnit Theory tests.
  • Build-First Workflow: Ensures the solution is built before tests are run, catching compile errors early.
  • Use Case: When refactoring a specific feature, you can use this Skill to run only the tests related to that feature, getting rapid feedback on your changes without waiting for a full test suite to complete.

Quick Start

Build the solution and then run tests for the 'UserServiceTests' class.

Frequently Asked Questions about dotnet-test

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

FAQPage Schema
How do I run specific .NET tests without executing the entire test suite?

You can run specific .NET tests selectively by using the `dotnet test` command with advanced filtering based on fully qualified method names, class names, or xUnit Theory parameter display names to accelerate your development feedback loop.

Can I filter xUnit Theory tests by their parameter values when running dotnet test?

Yes, selective test execution supports filtering xUnit Theory tests by their specific parameter display names, allowing you to target only the exact test data scenarios you are currently refining without rebuilding the entire solution.

Does this .NET test automation approach build the solution before running targeted tests?

Yes, it employs a build-first workflow that automatically builds the solution before executing the targeted tests, ensuring compile errors are caught early before wasting time on test execution.

What is the best way to run tests by category or class name during .NET refactoring?

The best way to run tests by category or class name is using selective `dotnet test` filtering, which catches compile errors in a build-first phase and then executes only the targeted tests for rapid feedback.

Why run targeted .NET tests instead of the full suite when refactoring a feature?

Running targeted tests instead of the full suite accelerates the development feedback loop by skipping unrelated tests, allowing you to get rapid feedback on your specific changes without waiting for the entire test suite to complete.

Do I need any specific test framework to use selective dotnet test filtering?

No external dependencies are required, but advanced filtering capabilities are specifically designed to support xUnit Theory parameters, fully qualified names, and display names within your existing .NET testing workflow.