dotnet-testing

Guide .NET testing strategies covering unit, integration, E2E, and performance frameworks.

1|1|Updated Mar 7, 2026

Search Tags:#testing #integration testing #code coverage #ui testing #performance testing #.net #xunit

Ready to run

npx skills add https://github.com/itsmichaelwest/agent-kit --skill dotnet-testing-itsmichaelwest

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance on .NET testing, from foundational unit testing to advanced integration, E2E, and performance testing strategies, ensuring robust and reliable software.

Core Features & Use Cases

Test Strategy: Defines unit vs. integration vs. E2E decision trees and test double selection.
Frameworks: Covers xUnit v3, WebApplicationFactory, Testcontainers, Playwright, and BenchmarkDotNet.
Quality Tools: Integrates Coverlet, ReportGenerator, Stryker.NET, and CRAP analysis for code coverage, reporting, mutation testing, and risk assessment.
Use Case: A developer needs to implement a new testing strategy for a complex .NET microservice, requiring guidance on choosing the right test types, setting up infrastructure, and ensuring code quality through coverage and mutation testing.

Quick Start

Use the dotnet-testing skill to define a test strategy for a new .NET microservice.

Frequently Asked Questions about dotnet-testing

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

FAQPage Schema

How do I structure a .NET testing strategy for a new microservice?▼

A .NET testing strategy should define decision trees for unit, integration, and E2E tests, select appropriate test doubles, and integrate quality tools like Coverlet and Stryker.NET to ensure robust microservice reliability.

What is the difference between unit, integration, and E2E testing in .NET?▼

Unit testing isolates components with test doubles, integration testing validates module interactions using WebApplicationFactory or Testcontainers, and E2E testing validates full user flows via Playwright to ensure comprehensive .NET application coverage.

How do I measure code coverage and test quality in .NET?▼

Measure .NET code coverage and test quality using Coverlet for raw metrics, ReportGenerator for readable reports, and Stryker.NET for mutation testing to evaluate test effectiveness and identify high-risk code via CRAP analysis.

Does BenchmarkDotNet work well for CI pipeline performance testing in .NET?▼

Yes, BenchmarkDotNet facilitates .NET performance testing and CI benchmarking by providing precise runtime measurements, allowing development teams to track performance regressions systematically within automated pipelines.

How do I set up integration testing for .NET using Testcontainers?▼

Set up .NET integration testing with Testcontainers to provision lightweight databases and dependencies dynamically, pairing it with xUnit and WebApplicationFactory to execute reliable, isolated module interaction tests.

What's the best way to automate UI testing in a .NET application?▼

Automate .NET UI testing using Playwright to simulate browser interactions and validate end-to-end user workflows, establishing reliable snapshot testing patterns to prevent visual regressions across application updates.