test-integration-api

End-to-end API integration tests mock downstream HTTP calls by bootstrapping a WebApplicationFactory test host, wiring up authentication, and using Flurl to intercept typed HTTP clients. This validates full request pipelines and routing within an isolated environment.

Testing ASP.NET Core controllers and routing with authentication is best handled by bootstrapping a fully wired test host. This approach exercises the complete request pipeline, validating authentication flows and integration scenarios across services.

Yes, you can use Flurl and typed HTTP clients to simulate real service interactions in API testing. The framework wires up HTTP dependency mocking capabilities to intercept downstream calls, allowing you to validate integration scenarios without live dependencies.

WebApplicationFactory supports isolating test environments for e2e-testing by bootstrapping a fully wired ASP.NET Core test host instance. It applies to scenarios that exercise controllers, routing, authentication, and downstream service interactions across the full request pipeline.

You need HTTP mocking capabilities for integration testing when validating full request pipelines that interact with downstream services. It allows you to simulate external service responses, ensuring tests remain isolated, deterministic, and independent of live network calls.