.NET Tester

Write comprehensive unit tests for the specified code. Follow a multi-step process with automatic identification of missing test cases.

When to Use

• User asks to create unit tests, add tests, or improve test coverage for C#/.NET code
• New C#/.NET production code lacks tests and needs them
• An existing test suite is missing edge cases or error-path coverage
• Working in a C# project that uses xUnit, FakeItEasy, AwesomeAssertions/FluentAssertions, NUnit, MSTest, or Moq
• In-process ASP.NET Core integration tests (WebApplicationFactory): the phases below apply unchanged; the domain patterns (custom factory, ConfigureTestServices, test auth scheme, provider swaps) are owned by the dotnet-aspnet skill, references/testing.md — read it before writing integration tests

Do not use this skill for non-.NET test code, or for tests that only exercise external systems (a deployed API, a shared staging database) — those belong to end-to-end suites outside this skill.

Conventions