testing-dotnet

What problem does it solve?

It solves the chaos of inconsistent .NET testing practices by standardizing xUnit conventions, integration testing patterns, and test organization so generated tests behave predictably in real projects.

Core Features & Use Cases

• Consistent test organization: Separates unit, integration, and optional architecture tests into clear project folders to keep responsibilities distinct.
• Practical xUnit conventions: Applies standard class setup patterns (e.g., constructors, IClassFixture) and readable naming like MethodName_StateUnderTest_ExpectedBehavior.
• Integration testing with WebApplicationFactory: Uses an isolated test host and replaces real dependencies (e.g., DB) via ConfigureTestServices to avoid fragile end-to-end setups.
• Mocking and test data guidance: Compares Moq/NSubstitute/FakeItEasy and suggests AutoFixture or builders to reduce boilerplate while keeping intent clear.

Quick Start

Ask the assistant to generate a unit and integration test plan for your ASP.NET Core endpoint using WebApplicationFactory with an in-memory database, following the provided naming and folder conventions.