From dotnet-artisan
Defines .NET test strategy and implementation patterns across xUnit v3, integration testing (WebApplicationFactory, Testcontainers), Aspire testing, Verify snapshot testing, Playwright E2E, BenchmarkDotNet, Coverlet code coverage, Stryker.NET mutation testing, and AOT WASM test compilation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/dotnet-artisan:dotnet-testingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Testing strategy, frameworks, and quality tooling for .NET applications. This consolidated skill spans 13 topic areas. Load the appropriate companion file from `references/` based on the routing table below.
agents/openai.yamlreferences/add-testing.mdreferences/aot-wasm.mdreferences/aspire-testing.mdreferences/benchmarkdotnet.mdreferences/ci-benchmarking.mdreferences/integration-testing.mdreferences/playwright.mdreferences/slopwatch.mdreferences/snapshot-testing.mdreferences/test-quality.mdreferences/testing-strategy.mdreferences/ui-testing-core.mdreferences/xunit.mdTesting strategy, frameworks, and quality tooling for .NET applications. This consolidated skill spans 13 topic areas. Load the appropriate companion file from references/ based on the routing table below.
Baseline dependency: references/testing-strategy.md defines the unit vs integration vs E2E decision tree and test doubles selection that inform all testing decisions. Load it by default whenever a testing approach needs to be chosen.
Most-shared companion: references/xunit.md covers xUnit v3 framework features used by integration, snapshot, and UI testing companions.
| Topic | Keywords | Description | Companion File |
|---|---|---|---|
| Strategy | unit vs integration vs E2E, test doubles | Unit vs integration vs E2E decision tree, test doubles selection | references/testing-strategy.md |
| xUnit | Facts, Theories, fixtures, parallelism | xUnit v3 Facts, Theories, fixtures, parallelism, IAsyncLifetime | references/xunit.md |
| Integration | WebApplicationFactory, Testcontainers, Aspire | WebApplicationFactory, Testcontainers, Aspire, database fixtures | references/integration-testing.md |
| Snapshot | Verify, scrubbing, API responses | Verify library, scrubbing, custom converters, HTTP response snapshots | references/snapshot-testing.md |
| Playwright | E2E browser, CI caching, trace viewer | Playwright E2E browser automation, CI caching, trace viewer, codegen | references/playwright.md |
| BenchmarkDotNet | microbenchmarks, memory diagnosers | BenchmarkDotNet microbenchmarks, memory diagnosers, baselines | references/benchmarkdotnet.md |
| CI benchmarking | threshold alerts, baseline tracking | CI benchmark regression detection, threshold alerts, baseline tracking | references/ci-benchmarking.md |
| Test quality | Coverlet, Stryker.NET, flaky tests | Coverlet code coverage, Stryker.NET mutation testing, flaky tests | references/test-quality.md |
| Add testing | scaffold xUnit project, coverlet, layout | Scaffold xUnit project, coverlet setup, directory layout | references/add-testing.md |
| Slopwatch | LLM reward hacking detection | Slopwatch CLI for LLM reward hacking detection | references/slopwatch.md |
| AOT WASM | Blazor/Uno WASM AOT, size, lazy loading | Blazor/Uno WASM AOT compilation, size vs speed, lazy loading, Brotli | references/aot-wasm.md |
| UI testing core | page objects, selectors, async waits | Page object model, test selectors, async waits, accessibility testing | references/ui-testing-core.md |
| Aspire testing | DistributedApplicationTestingBuilder, Aspire test host | Aspire test host, service HTTP clients, resource health | references/aspire-testing.md |
npx claudepluginhub novotnyllc/dotnet-artisan --plugin dotnet-artisanDeciding how to test .NET code. Unit vs integration vs E2E decision tree, test doubles.
Testing strategy for .NET 10 applications using xUnit v3, WebApplicationFactory for integration tests, Testcontainers for real database testing, Verify for snapshot testing, and the AAA pattern.
Provides testing strategies including test pyramid, TDD/BDD, unit/integration/E2E patterns, mocking strategies, test data factories, snapshot testing, and mutation testing. Use for designing test strategies, writing tests, or improving coverage.