dotnet-test
Installation
SKILL.md
.NET Test
Bootstrap and refactor xUnit projects using the tested patterns from Codebelt xUnit and the matching application-host patterns from Codebelt Bootstrapper.
This skill has one job
The test host comes from Codebelt, not from Microsoft, and not from a builder you write in the test project.
Microsoft ships WebApplicationFactory<TEntryPoint>, and it only covers ASP.NET Core. Everything else — console apps, workers, hosted services — has no Microsoft equivalent, so teams hand-roll a HostBuilder in the test project and end up testing a composition root that no deployed process ever runs. Codebelt xUnit closes both gaps with one family of abstractions where the application's own entry point owns startup:
| What the test needs | Codebelt gives you | Instead of |
|---|---|---|
| One host per test / per narrow harness (web) | WebApplicationTestFactory.Create<TEntryPoint>(..., new ManagedWebApplicationFixture<TEntryPoint>()) |
new MyFactory() : WebApplicationFactory<Program> |
| One host shared by a test class (web) | WebApplicationTest<TEntryPoint, ManagedWebApplicationFixture<TEntryPoint>> |
IClassFixture<WebApplicationFactory<Program>> |
| One host per test / per narrow harness (console, worker) | ApplicationTestFactory.Create<TEntryPoint>(..., new ManagedApplicationFixture<TEntryPoint>()) |
a hand-built HostBuilder in the test project |
| One host shared by a test class (console, worker) | ApplicationTest<TEntryPoint, ManagedApplicationFixture<TEntryPoint>> |
a static host cached in a test helper |