dotnet-test

Create and organize xUnit tests for .NET solutions with mirrored project structure.

1|Updated Feb 10, 2026

Search Tags:#testing #dotnet #mocking #xunit #unit-tests #test-project #mirroring-structure

Ready to run

npx skills add https://github.com/landim32/awesome-ai-skills --skill dotnet-test-landim32

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-test
Source: https://github.com/landim32/awesome-ai-skills/tree/main/skills/dotnet-test
Command: npx skills add https://github.com/landim32/awesome-ai-skills --skill dotnet-test-landim32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and organization of unit tests for .NET solutions using xUnit, reducing boilerplate and ensuring consistent structure.

Core Features & Use Cases

Creates a single {SolutionName}.Tests project if missing, named following the solution convention.
Mirrors the source project layout across Domain, Application, Infra, and API layers to map tests 1:1 with source classes.
Generates test files and stubs for new or updated classes, and wires necessary project references and common mocking patterns.

Quick Start

Create or update the test project to align with the solution structure and generate tests for existing classes.

Frequently Asked Questions about dotnet-test

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

FAQPage Schema

How do I organize xUnit tests across multiple .NET solution layers?▼

To organize xUnit tests across .NET layers, you can create a single {SolutionName}.Tests project that mirrors your Domain, Application, Infra, and API folder structure, mapping one test class per source class.

What is the best way to mirror source project layout in a .NET test project?▼

Mirroring source project layout in a .NET test project involves generating a matching Domain/Application/Infra/API folder structure within a central test project, ensuring a 1:1 mapping between source classes and test files.

How do I set up Moq for mocking in a new .NET xUnit test project?▼

To set up Moq for mocking in a .NET xUnit test project, the project must be created with necessary core project references wired, integrating Moq patterns automatically for testing Domain and Application classes.

Can I use this to generate test stubs for existing .NET classes?▼

Yes, you can generate test files and stubs for existing .NET classes by creating or updating the test project to align with your solution structure, automatically wiring necessary project references.

Does this .NET testing approach create separate test projects for each layer?▼

No, this .NET testing approach creates a single {SolutionName}.Tests project rather than separate projects, referencing the core projects and enforcing a mirrored folder structure across all layers.

When do I need to reorganize unit tests in a .NET solution?▼

You need to reorganize unit tests in a .NET solution when creating, updating, or reorganizing source classes, ensuring the central xUnit test project continuously mirrors the Domain, Application, Infra, and API layout.