dotnet-testing-strategy

Select .NET testing strategies using a decision tree for unit, integration, and end-to-end tests.

71|10|Updated Feb 11, 2026

Search Tags:#code quality #testing #integration testing #unit testing #test strategy #.net

Ready to run

npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-testing-strategy-wshaddix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-testing-strategy
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-testing-strategy
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-testing-strategy-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a clear decision framework for selecting the appropriate testing strategy in .NET development, ensuring efficient and effective quality assurance.

Core Features & Use Cases

Test Type Selection: Guides users through choosing between unit, integration, and end-to-end tests based on dependencies and criticality.
Organization & Naming: Offers conventions for structuring test projects, classes, and individual test methods for clarity and maintainability.
Test Double Guidance: Explains when and how to use stubs, mocks, and fakes to isolate code under test.
Use Case: When developing a new feature, use this Skill to determine whether to write a fast unit test, a more comprehensive integration test with a real database, or a full end-to-end test simulating user interaction.

Quick Start

Use the dotnet-testing-strategy skill to decide whether to write a unit test or an integration test for a new repository method.

Frequently Asked Questions about dotnet-testing-strategy

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

FAQPage Schema

How do I choose between unit and integration tests in .NET?▼

To choose between unit and integration tests in .NET, evaluate dependencies and criticality. A decision tree helps determine if a fast unit test or a comprehensive integration test with a real database is appropriate.

What is the best way to organize .NET test projects and naming conventions?▼

Organizing .NET test projects requires clear conventions for structuring classes and methods. Following standardized naming conventions for test projects ensures long-term maintainability and clarity across the software engineering lifecycle.

When should I use stubs, mocks, or fakes for .NET testing?▼

Use stubs, mocks, or fakes in .NET testing to isolate code under test. Decide based on whether you need to verify state or interactions, ensuring the test double strategy aligns with your overall test pyramid.

What are common .NET testing anti-patterns and how do I avoid them?▼

Common .NET testing anti-patterns include overusing test doubles and writing brittle end-to-end tests. Avoid them by performing a cost-benefit analysis for different test types to ensure efficient and effective quality assurance.

Does my .NET testing strategy need end-to-end tests for new repository methods?▼

Your .NET testing strategy may not need end-to-end tests for new repository methods. Evaluate if a fast unit test or a focused integration test with a real database provides sufficient coverage without high execution costs.