dotnet-test

Run and filter .NET tests with the dotnet test CLI.

4|1|Updated Dec 29, 2025
One-click install
npx skills add https://github.com/DoubleslashSE/claude-marketplace --skill dotnet-test-doubleslashse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-test
Source: https://github.com/DoubleslashSE/claude-marketplace/tree/main/Plugins/dotnet-developer/skills/dotnet-test
Command: npx skills add https://github.com/DoubleslashSE/claude-marketplace --skill dotnet-test-doubleslashse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates and analyzes .NET test execution using the dotnet test CLI to streamline testing workflows.

Core Features & Use Cases

  • Unified test execution: Run tests across solutions and projects with consistent options.
  • Advanced filtering: Filter tests by FullyQualifiedName, Category/Trait, ClassName, or Namespace to target specific scenarios.
  • Diagnostics and outputs: Configure verbosity, logs, results formats (trx, html, json), and code coverage per project.
  • Use Case: In a CI pipeline, execute unit and integration tests with specific filters, aggregate results, and generate reports.

Quick Start

dotnet test

Frequently Asked Questions about dotnet-test

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

FAQPage Schema
How do I run .NET tests across multiple projects with specific filters?

You can configure .NET test outputs by setting verbosity levels, logs, and results formats like trx, html, or json per project using standard dotnet test options and configuration files.

Does the dotnet test CLI support filtering by category or trait?

Yes, dotnet test CLI supports filtering by Category or Trait, allowing you to target specific test scenarios across your solutions and projects without running the entire suite.

Do I need the .NET SDK installed to run tests with this approach?

Yes, you need the .NET SDK installed locally or in your CI environment to execute dotnet test commands and generate reproducible test diagnostics and results.

What's the best way to generate test reports in a CI pipeline?

The best way to generate CI reports is executing dotnet test with configured output formats like trx, html, or json, aggregating results to produce consistent test diagnostics and coverage data.

Why are my dotnet test results not reproducible across environments?

Test results may lack reproducibility if standard dotnet test options and configuration files are not consistently applied across local and CI environments to manage diagnostics and outputs.