dotnet-add-testing

Scaffold xUnit test projects with Coverlet coverage for .NET solutions.

71|10|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-add-testing-wshaddix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-add-testing
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-add-testing
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-add-testing-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the setup of essential testing infrastructure for .NET projects, saving developers time and ensuring consistency.

Core Features & Use Cases

  • Test Project Scaffolding: Creates xUnit test projects with conventional naming and directory structures.
  • Code Coverage Setup: Integrates Coverlet for code coverage analysis.
  • Build Configuration: Configures Directory.Build.props for shared test settings and CPM for package management.
  • Use Case: When starting a new .NET project or adding testing to an existing one, use this Skill to quickly set up a robust testing foundation, including unit and integration test projects, and configure code coverage reporting.

Quick Start

Use the dotnet-add-testing skill to scaffold xUnit test projects and configure code coverage for your .NET solution.

Frequently Asked Questions about dotnet-add-testing

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

FAQPage Schema
How do I scaffold an xUnit test project for a .NET solution?

Scaffolding xUnit test projects involves creating the project, integrating it into your .NET solution, and applying conventional directory structures for both unit and integration tests.

What is the best way to configure Coverlet for code coverage in .NET?

Configuring Coverlet for code coverage is handled by integrating the package into your test projects and managing it through centralized build properties using Directory.Build.props and Directory.Packages.props.

How do I set up Directory.Build.props for centralized .NET package management?

Setting up Directory.Build.props for centralized package management (CPM) involves configuring shared test settings and package versions across your .NET solution to ensure consistent build configurations.

Can I add both unit and integration test projects to an existing .NET app?

Yes, you can add both unit and integration test projects to an existing .NET application, and the skill will integrate them directly into your current solution with conventional naming structures.

Does .NET test scaffolding support centralized package management?

Yes, .NET test scaffolding supports centralized package management by configuring Directory.Packages.props to control package versions and Directory.Build.props to apply shared test settings across projects.