dotnet-test-api

To set up .NET API integration tests separately, this Skill bootstraps a dedicated ApiTests project wired to your DTO project and provides shared test collection fixtures. This isolates end-to-end HTTP tests from unit tests, preventing conflicting lifecycles and tangled dependencies.

Sharing authentication across .NET integration tests is achieved using reusable ApiTestFixture and ApiTestCollection classes. This approach provides shared authentication state across test cases, supporting multiple presets like Generic JWT, NAuth, OAuth2 client credentials, and API keys.

Yes, this API testing approach supports OAuth2 client credentials and environment-based secrets. It provides configurable authentication presets that securely manage credentials based on your environment, enabling seamless end-to-end API testing against staging or production configurations.

Yes, you can use xUnit with Flurl for controller-level integration testing in .NET. This Skill leverages xUnit test collection fixtures and Flurl to execute end-to-end HTTP requests against external APIs, validating behavior across multiple DTOs.

Keeping external API integration tests in a standalone project prevents tangled test lifecycles and conflicting authentication concerns. It separates slow end-to-end HTTP tests from fast unit tests, ensuring your DTO project integration remains clean and maintainable.