dotnet-testing

Choosing a .NET testing strategy involves deciding when to use unit, integration, functional, or end-to-end tests for a given scenario. This Skill evaluates your project to turn test planning into actionable implementation guidance, ensuring deterministic and maintainable validation across the suite.

Setting up xUnit v3 fixtures and async lifecycle hooks requires applying specific framework assertion patterns and lifecycle design. This Skill provides framework guidance to scaffold test project structure, manage test isolation, and enforce stable, maintainable validation across your suite.

Yes, this approach works with WebApplicationFactory and Aspire testing for realistic API and service coverage. The Skill guides integration and E2E setups using Testcontainers and Playwright to validate browser flows and service dependencies effectively.

The best way to measure .NET test coverage and prevent flaky tests is by applying quality gates using Coverlet and mutation testing. This Skill helps add snapshot testing and BenchmarkDotNet benchmarks to protect behavior, catch regressions, and simplify debugging.

Yes, you can use Playwright E2E and BenchmarkDotNet in the same .NET test project. This Skill covers both browser flow validation and performance benchmarking, ensuring your test setup enforces stable, maintainable validation across functional and performance scenarios.