dotnet-testing

Name: dotnet-testing
Author: novotnyllc

github.com/novotnyllcTesting & quality234194 installsUpdated 2w ago

About dotnet-testing

dotnet-testing is a .NET skill for planning and implementing application tests and quality checks. It organizes guidance on test strategy, xUnit, integration and browser testing, benchmarks, coverage, mutation testing, and UI test patterns.

Key features

01Unit, integration, and E2E strategy
02xUnit v3 authoring guidance
03Integration and Playwright testing
04Benchmarking and CI regression checks
05Coverage, mutation, and flaky-test guidance
06Cross-framework UI testing patterns

Use cases

01Choosing a test type and test doubles
02Adding xUnit tests to a project
03Testing APIs and browser workflows
04Tracking performance and test quality

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/novotnyllc/dotnet-artisan --skill dotnet-testing

After installing, type/dotnet-testingin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

agents/

openai.yaml

references/

add-testing.md

aot-wasm.md

aspire-testing.md

benchmarkdotnet.md

ci-benchmarking.md

integration-testing.md

playwright.md

slopwatch.md

snapshot-testing.md

test-quality.md

testing-strategy.md

ui-testing-core.md

xunit.md

Details

From the project README

dotnet-testing

Overview

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.

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.

Routing Table

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

Scope

Test strategy and architecture (unit, integration, E2E)
xUnit v3 test authoring
Integration testing (WebApplicationFactory, Testcontainers)
E2E browser testing (Playwright)
Snapshot testing (Verify)
Benchmarking (BenchmarkDotNet, CI gating)
Quality (coverage, mutation testing)
Cross-framework UI testing patterns
Test scaffolding

Out of scope

UI framework-specific testing (bUnit, Appium) -> dotnet-ui
CI/CD pipeline configuration -> dotnet-devops
Performance profiling -> dotnet-tooling

Comments

Markdown supported

Details

Author: novotnyllc
Repository: novotnyllc/dotnet-artisan
Category: Testing & quality
Installs: 194
GitHub stars: 234

Report

More skills

All skills

hyperframes-cli

github.com/heygen-com

1.3M

HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, compare, grade-compare, preview, play, render, publish, feedback, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, tts, or remove-background, or when troubleshooting the HyperFrames build/render environment. Entry point for AWS Lambda cloud rendering (hyperframes lambda deploy / render / progress / destroy / policies / sites).

tdd

github.com/mattpocock

1.2M

Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

anti-ui-slop

uizze.com

932.8k

Stop coding agents from shipping generic UI. Use UIZZE's 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".

diagnosing-bugs

github.com/mattpocock

856.9k

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.