What problem does it solve? Writing integration tests for ASP.NET Core endpoints requires repetitive setup of WebApplicationFactory, in-memory databases, auth bypasses, and seeding logic. This Skill codifies the project's exact conventions so new endpoint tests follow the established pattern without re-deriving the infrastructure each time. ## Core Features & Use Cases - Endpoint Test Scaffolding: Generates a <Feature>EndpointsTests class per endpoint group, derived from IntegrationTestBase with IClassFixture sharing a TestWebApplicationFactory. - Seeding and Cleanup Patterns: Uses WithUowAsync helpers and BatchHardDeleteAsync for per-test cleanup, plus ignoreQueryFilters: true to assert on soft-deleted rows. - Validation and Auth Coverage: Asserts RFC 7807 ProblemDetails (Code, Status, Errors) for validation, conflict, and not-found cases, and handles [Authorize] endpoints via the pre-wired TestAuthHandler. - Use Case: After adding a new Orders module with CRUD endpoints, ask the Skill to add integration tests; it produces OrdersEndpointsTests.cs covering happy path, validation failure, conflict, and not-found scenarios, runnable via bun run test:api:int. ## Quick Start Add integration tests for the new Orders endpoints in packages/api following the backend integration test conventions.
